IRCloggy #git 2019-06-11

Logs Search ←Prev date Next date→ Channels Documentation

Provider of IRC logs since 2005.
WARNING: As Freenode became unjoinable and lost all warnings in topics, we cannot log channels on Freenode anymore.

2019-06-11

tgunr left00:00
tgunr joined00:00
nerosnm left00:02
tgunr left00:08
sozuba left00:11
plantroon left00:14
impermanence left00:16
greatgatsby left00:18
m0viefreak left00:18
plantroon joined00:19
xcm left00:20
xcm joined00:21
mooasaurus left00:23
oatmealraisin left00:23
mooasaurus joined00:23
smitop left00:26
ZRocket joined00:27
impermanence joined00:33
misuto left00:34
misuto joined00:37
devster31 left00:38
mud joined00:38
cliluw joined00:44
clime left00:44
misuto left00:47
devster31 joined00:48
javango joined00:49
Copenhagen_Bram left00:50
cdown joined00:50
nerosnm joined00:50
javango Hello. Do git branches have some kind of comment? I want to attach some info to a branch00:51
Not to commit00:51
Copenhagen_Bram joined00:51
fphilipe_ joined00:52
eb0t joined00:52
moldybits left00:53
Abbott left00:54
nerosnm left00:55
thiago joined00:55
igemnace joined00:56
nerosnm joined00:57
bradleyprice left00:58
bradleyprice joined00:59
Sasazuka left01:02
bradleyprice left01:03
misuto joined01:04
Bobdude joined01:04
Noldorin joined01:05
Noldorin left01:07
jrnieder javango: check out "git branch --edit-description"01:07
howdoi joined01:08
moldybits joined01:08
jubal left01:08
anv8l3 joined01:12
anv8l3 hey all, might be slightly offtopic but... tortoisegit. How in the world are you supposed to see what is actually stashed?01:12
jrnieder have you tried GitCheetah? :)01:13
anv8l3 no, if i give up on tortoise i'll just do it all on the command line01:14
jrnieder oh hm, cheetah doesn't appear to have been updated for years01:14
anv8l3 this specific window is the worst i've seen in tortoise01:14
jrnieder short answer is that tortoise is very svn-centric01:14
anv8l3 when I click the obvious things, it doesn't show me anything close to what i stashed01:14
boombatower left01:14
anv8l3 it lists tons of other changed files, presumably looking at other branches or all changes since the stash...01:15
nerosnm left01:15
jrnieder there's also https://gitextensions.github.io01:16
anv8l3 i'm starting to wonder if this is a situation where nobody has this problem because everyone abandoned the software before they hit this point01:17
jrnieder well, to be clear, lots of people do use tortoisegit01:17
I just don't understand them ;-)01:17
others may have more helpful answers01:17
anv8l3 i found something i'd consider a workaround... whether it's considered a feature is TBD...01:18
jrnieder sounds like a reasonable improvement to make to tortoisegit, btw01:19
cdown left01:19
anv8l3 you can copy "full data" to the clipboard... so now I can view this in a text editor instead of the UI01:20
but it is the actual list, so problem solved i guess. thanks for the suggestions.01:20
jrnieder sure thing, sorry I don't have better advice01:21
anv8l3 left01:21
libertyprime joined01:22
F0rTex left01:23
F0rTex joined01:24
fphilipe_ left01:26
bradleyprice joined01:30
tufteddeer left01:31
tufteddeer joined01:32
cdown joined01:32
Cheaplogic left01:38
ygivenx left01:39
leb joined01:40
cdown left01:43
freeman42y left01:44
nerosnm joined01:44
Cabanossi left01:44
Cabanossi joined01:47
duderonomy joined01:50
fphilipe_ joined01:55
lempamo joined01:56
yonder joined01:57
jstimm left02:00
bradleyprice left02:05
bradleyprice joined02:06
agowa338 left02:09
bradleyprice left02:10
nerosnm left02:10
queip left02:17
rustyshackleford joined02:20
queip joined02:23
elsheepo joined02:28
esrse joined02:29
fphilipe_ left02:30
davidfetter_work left02:34
lagothrix left02:36
lagothrix joined02:36
elsheepo left02:37
dviola left02:38
NightStrike how do I update my branch from master using the method that replays all my work on top of master instead of creating a separate merge commit?02:38
I was going to try "git rebase master", but I was afraid that would lose my tracking to upstream origin/branch02:39
pr0ton left02:42
NightStrike nevermind, I figured it out02:43
bradleyprice joined02:44
ferdna left02:53
UniFreak joined02:53
mud left02:54
CryptoDavid left02:57
bradleyprice left02:58
supernovah how do you show which submodule a commit has referenced02:59
I just get, exists on disk but not in <commit>02:59
but if I git diff I get the hash02:59
sz0 joined03:02
mns left03:02
mns joined03:03
rjsalts_rjsalts03:05
bradleyprice joined03:06
MACscr left03:10
zaricythe left03:10
javango jrnieder, thanks you! Although it's pity that this description cannot be pushed :(03:12
bradleyprice left03:12
bradleyprice joined03:18
nic-hartley left03:21
Newami left03:22
fphilipe_ joined03:26
fflam left03:31
bradleyprice left03:32
fflam joined03:32
leb left03:34
oatmealraisin joined03:35
lempamo left03:36
ghoti left03:39
jcbitter joined03:43
Anthaas left03:43
Anthaas joined03:44
bradleyprice joined03:44
mns left03:46
davidfetter_work joined03:46
mns joined03:47
orbyt_ left03:50
bradleyprice left03:50
oatmealraisin left03:51
impermanence left03:53
jcbitter left03:55
Goplat joined03:55
jcbitter joined03:56
fphilipe_ left03:59
bradleyprice joined03:59
nurdie joined04:00
jcbitter left04:01
jcbitter joined04:02
bradleyprice left04:03
leah2 left04:05
hussam joined04:07
cdown joined04:07
z|bandito left04:12
ZRocket left04:14
cdown left04:14
fphilipe_ joined04:15
wgrant joined04:18
xcm left04:19
xcm joined04:20
leah2 joined04:20
cdown joined04:21
SkarmoutsosV joined04:24
bradleyprice joined04:35
rustyshackleford where I work requires me to set $http_proxy for git to work correctly04:42
is there anything more secure? Ideally I'm not leaving passwords in plain text (proxy requires authentication)04:43
but setting that variable in bash_profile seems to be the best I can do04:43
bradleyprice left04:45
jubal joined04:47
matsaman joined04:48
matheusmoreira left04:48
matsaman left04:48
matheusmoreira joined04:49
comptroller left04:53
davidfetter_work left04:55
pks_ joined05:00
pks left05:02
pks_pks05:02
pr0ton joined05:05
comptroller joined05:05
bradleyprice joined05:11
bradleyprice left05:16
libertyprime left05:17
fphilipe_ left05:19
zlogan2003 joined05:21
bradleyprice joined05:22
kjartan left05:22
Inline left05:22
zlogan left05:24
kjartan joined05:27
bradleyprice left05:27
hojang joined05:27
wgrant left05:28
tufteddeer left05:30
tufteddeer joined05:31
SkarmoutsosV left05:35
gloomy joined05:35
SkarmoutsosV joined05:36
hojang left05:37
mat001 joined05:38
wgrant joined05:38
libertyprime joined05:39
bradleyprice joined05:43
fjellfras joined05:45
crackin joined05:46
bradleyprice left05:47
Copenhagen_Bram left05:47
hojang joined05:51
bradleyprice joined05:56
BeerLover joined05:56
crackin left05:57
tufteddeer left05:58
osse rustyshackleford: man gitcredentials05:59
gitinfo rustyshackleford: the gitcredentials manpage is available at https://gitirc.eu/gitcredentials.html05:59
osse maybe some of that can help05:59
tufteddeer joined05:59
bradleyprice left06:00
hojang left06:01
nast joined06:05
Kaisyu7 left06:12
nast left06:12
Goplat left06:13
fphilipe_ joined06:13
sQVe joined06:13
hojang joined06:15
bradleyprice joined06:17
Kaisyu7 joined06:17
Mattiaslndstrm joined06:17
sozuba joined06:18
andrzejv joined06:20
bradleyprice left06:21
xcm left06:23
xcm joined06:24
Noti joined06:25
thefatma joined06:26
salad joined06:26
hojang left06:28
gde33 left06:28
gde33 joined06:29
cdown left06:33
cdown joined06:33
fphilipe_ left06:35
v01d4lph4 joined06:36
bradleyprice joined06:37
hojang joined06:38
bradleyprice left06:42
jcbitter left06:44
Newami joined06:44
n3wborn joined06:45
kevr joined06:45
jcbitter joined06:45
hojang left06:47
ghoti joined06:48
maxb_ joined06:49
maxb_ left06:49
chele joined06:55
MACscr joined06:55
g00s joined06:55
javango left06:55
hojang joined06:57
bradleyprice joined06:59
stdedos left06:59
stdedos joined06:59
lankanmon left06:59
moei joined07:00
lankanmon joined07:01
bradleyprice left07:03
fphilipe_ joined07:06
cdown left07:06
staafl_ joined07:06
mayurvpatil joined07:09
staafl_ left07:11
Eryn_1983_FL left07:12
staafl_ joined07:13
nurdie left07:16
ryez joined07:16
queip left07:17
hofmann3900 left07:17
is_null joined07:18
pr0ton left07:18
igemnace left07:18
bradleyprice joined07:19
thefatma left07:21
Bobdude left07:22
Jackneill joined07:22
bradleyprice left07:24
queip joined07:24
mayurvpatil left07:24
hio joined07:25
BeerLover left07:26
Eryn_1983_FL joined07:26
yonder left07:27
Jackneill left07:29
duderonomy left07:29
Jackneill joined07:30
thiago left07:30
igemnace joined07:31
mat001 left07:32
duderonomy joined07:32
howdoi left07:32
Jackneill left07:35
Jackneill joined07:36
sgnls joined07:37
T_UNIX joined07:38
ryez left07:39
rustyshackleford left07:39
cdown joined07:40
bradleyprice joined07:40
BeerLover joined07:42
jwynn6 left07:43
hojang left07:43
mayurvpatil joined07:44
g00s left07:44
g00s joined07:44
bradleyprice left07:45
sQVe left07:45
duderonomy left07:46
Jackneill left07:47
SkarmoutsosV left07:48
jwynn6 joined07:48
Jackneill joined07:48
SkarmoutsosV joined07:48
Jackneill left07:49
Jackneill joined07:50
is_null_ joined07:51
thefatma joined07:52
DisruptiveNL joined07:52
tufteddeer left07:54
is_null left07:55
tufteddeer joined07:55
g00s left07:56
sbeyer joined07:57
SkarmoutsosV left07:58
inovas joined07:58
seebyr joined08:01
bradleyprice joined08:01
Newami left08:02
flughafen joined08:03
flughafen i accidently did a git checkout origin/foobranch08:03
then i did git co -, and git co foobranch but now it says error:pathspec 'foobranch' did not match any files known to git08:04
sbeyer left08:04
osse where were you before you made that mistake?08:04
Newami joined08:05
flughafen osse: master08:05
osse I assume git co - took you there?08:05
flughafen yeah08:05
bradleyprice left08:06
flughafen OOOOOOOOHGb08:06
i know what it is08:06
i'm pretty sure08:06
i haver a folder called foobranch08:06
osse try git checkout foobranch --08:06
flughafen but it's not tracked yet08:06
osse with the --08:06
flughafen ok.08:06
that worked.08:06
thanks08:06
DisruptiveNL_ joined08:07
DisruptiveNL left08:07
hojang joined08:10
Rubin joined08:11
mikecmpbll joined08:11
floppydh joined08:12
Mike11 joined08:15
nikivi left08:30
ghost43_ joined08:36
ghost43 left08:37
hojang left08:39
knullare left08:39
mayurvpatil left08:41
victorqueiroz left08:42
cdown left08:42
agowa338 joined08:44
dege joined08:45
osse I have a file with mixed line endings. I converted them all to CRLF and committed the file. The file was actually committed as CRLF and not converted to LF. Why did this happen when core.autocrlf is true?08:46
git add --renormalize works, but I don't see why that's necessary in this case08:47
pyfgcr joined08:47
ghoti left08:49
osse Ahh... If I git rm the file and then git add it again in a separate commit everything works as expected08:50
realies left08:50
hojang joined08:51
realies joined08:51
flaviodesousa joined08:53
flaviodesousa left08:54
flaviodesousa joined08:54
osse So I guess the fact that it was already present and screwed up in git's object store made git think "fuck it"08:54
flaviodesousa left08:54
flaviodesousa joined08:55
clime joined08:55
flaviodesousa left08:55
flaviodesousa joined08:56
flaviodesousa left08:56
cdown joined08:56
flaviodesousa joined08:57
flaviodesousa left08:57
flaviodesousa joined08:58
flaviodesousa left08:58
n3wborn left09:04
sQVe joined09:05
nikivi joined09:05
agowa338 osse: just add a .gitattributes files and this wont happen again.09:07
YuGiOhJCJ left09:07
osse Yes I know. Very tempted to do that. Big old repo with lots of crap09:09
I'm just shy09:09
BoneTone left09:12
cd joined09:12
queip left09:13
agowa338 Just do it, nothing exiting will break, only new files and you always have the option of just putting it into your local repo and never submit it upstream ;-)09:13
BoneTone joined09:14
osse Putting it in my local repo doesn't achieve much. I alreay have autocrlf true09:14
agowa338 Just rebase the commit containing it always on top of your working tree and strip it from feature branches before merge.09:14
osse easier to use .git/info/attributes then :P09:14
agowa338 yea, that also works. I thought of some origin/upstream split, where origin is your fork and upstream is the main project, but if you only have local and remote that works too.09:15
crackin joined09:17
catsup left09:18
catsup joined09:18
queip joined09:19
catsup left09:19
catsup joined09:20
is_null_ left09:21
crackin left09:22
SkarmoutsosV joined09:23
queip left09:26
is_null joined09:28
hojang left09:34
thefatma left09:37
libertyprime left09:39
fphilipe_ left09:41
seebyrsbeyer09:41
Xatenev joined09:42
Xatenev helo09:42
so on friday i had a local branch that was similar to the respective origin/ branch09:43
OtakuSenpai joined09:43
Xatenev today i do `git fetch` and `git rebase` on that origin branch and i get a conflict09:43
the only possibility how that happens is if someone has reset the branch, no?09:43
I don't see how I would get a conflict otherwise09:43
git status saying the branches have diverged09:43
by 16 and 236 commits09:44
BeerBuddy joined09:47
selckin if you didn't have local commits, then that sounds likely, else those could conflict09:48
!reflog09:48
gitinfo The git reflog (`git log -g`) temporarily (90 days by default) snapshots your branch states at each operation that changes the branch, making it easy to undo e.g. merges and rebases. The usual warnings about !rewriting/undoing history apply. See http://sethrobertson.github.com/GitFixUm/ for full details.09:48
BeerLover left09:48
Xatenev selckin, yeap i dont have any local commits09:48
it was clean when i left on friday .p09:48
is_null left09:48
_ikke_ Or someone rewrote history09:49
Xatenev _ikke_, yea that happens with reset right09:49
_ikke_ yes09:49
Xatenev suire they could rewrite it otherwise too.. hmm09:49
tribly left09:50
jcbitter left09:50
tribly joined09:50
thefatma joined09:52
Xatenev _ikke_, selckin do you know if i can find out what happened?09:52
with reflog or somethign09:52
selckin fetch output probably told you09:52
_ikke_ yes09:52
and that09:52
Xatenev fetch said "refresh forced"09:52
.. or something like that.. my git is in my native language :X09:53
_ikke_ that sounds like history rewriting09:53
tufteddeer left09:53
Xatenev localBranch -> originBranch (refresh forced)09:53
_ikke_ forced update is what I believe git would say in english09:53
Xatenev yeah sounds correct :P09:54
jcbitter joined09:55
lacrymology joined09:55
tribly left09:55
mayurvpatil joined09:55
tribly joined09:56
v01d4lph4 left09:56
agowa338 left09:56
mowcat joined09:57
Ayo joined09:59
OtakuSenpai left10:00
lankanmon left10:00
jcbitter left10:00
jcbitter joined10:01
averell left10:02
zamba left10:03
steven left10:03
steven joined10:06
fphilipe_ joined10:07
hojang joined10:08
thefatma left10:11
zamba joined10:11
thefatma joined10:11
is_null joined10:13
bsanford joined10:17
tribly left10:19
tribly joined10:20
bsanford left10:20
dcpc007 Hi, is it possible to easely find the commit from where a current branch diverge ?10:21
(to make a reset --hard on all current branch work only10:21
(it's for a #git-fr user asking)10:22
alyptik left10:22
_ikke_ dcpc007: if you know the branch where you merged from: git merge-base <base> <branch>10:22
dcpc007 ha thx, never seen merge-base10:22
DisruptiveNL joined10:23
SpeakerToMeat left10:24
dcpc007 i sent him.10:25
DisruptiveNL_ left10:25
Xatenev left10:26
arecaceae left10:26
arecaceae joined10:27
cdown left10:27
bradleyprice joined10:27
crackin joined10:29
libertyprime joined10:29
hojang left10:29
DisruptiveNL left10:29
DisruptiveNL joined10:30
jab416171 left10:31
SpeakerToMeat joined10:32
bradleyprice left10:32
thefatma left10:32
crackin left10:33
OtakuSenpai joined10:36
SkarmoutsosV left10:39
zamba left10:41
zamba joined10:43
BPL joined10:44
queip joined10:44
BPL Hi guys, I'd like to reset a bunch of repos and I've tried either `git checkout -- .` or `git reset --hard` but neither of these commands won't remove unstaged folders, how can i reset a repo completely?10:45
osse BPL: combine with git clean10:45
BPL osse: `git reset --hard && git clean -f` ? this won't do... :/10:46
hojang joined10:48
bradleyprice joined10:48
is_null left10:49
osse why not?10:49
You probably want -fdx10:51
BPL mmm, hold on, maybe my question wasn't correct... I meant those command won't remove "untracked folders", not "unstaged folders".10:51
_ikke_ -x would also remove ignored files10:51
BPL it seems `git reset --hard && git clean -fdx` works!10:52
bradleyprice left10:53
rsrx joined10:54
GyrosGeier hm10:54
sQVe left10:54
sQVe joined10:55
GyrosGeier can I invert "git bisect run"?10:56
_ikke_ you can rename the terms you use10:56
queip left10:57
GyrosGeier I want to find the commit where it was fixed10:57
I can just rewrite the script10:57
but if I can say "invert good/bad result from script", then I can reuse the existing one10:58
(which has different places with exit codes)10:58
_ikke_ git bisect start --term-new fixed --term-old broken10:58
osse GyrosGeier: I would just use it as normal and invert the meanings of good and bad in my head10:58
but that also works10:58
GyrosGeier my point is: the script returns 0 for good and 1 for bad as exit code11:00
osse oh11:00
GyrosGeier and 125 for skip11:00
I have a script attached to the bug report that I used to find the first bad commit11:00
now I'd like to use the exact same script to find the first good commit11:01
lankanmon joined11:02
GyrosGeier in the long run I'd like to automate that for all bug reports11:02
osse git bisect run sh -c 'the_script; ret=$?; if [ $ret -eq 125 ]; exit 125; fi; [ $ret -eq 1 ]'11:02
GyrosGeier mmh11:03
that should work11:03
hojang left11:03
osse I would prefer git bisect run the_script --flip-exit-codes11:04
GyrosGeier makes a mental note to add a flag11:04
GyrosGeier exactly11:04
emsjessec joined11:04
GyrosGeier and/or a "--find-bad-range" mode11:04
where you have atwo good and one bad commits at start, and it does two bisects back-to-back11:05
alyptik joined11:06
perrier-jouet left11:07
hojang joined11:07
paws_ joined11:09
bradleyprice joined11:09
queip joined11:11
fphilipe_ left11:11
thefatma joined11:12
hojang left11:13
hojang joined11:13
bradleyprice left11:14
BeerLover joined11:16
abelvesa joined11:16
BeerBuddy left11:17
oxymoron93 joined11:19
Newami left11:23
Ayo left11:28
hojang left11:28
hojang joined11:29
fjellfras left11:29
tchan joined11:30
bradleyprice joined11:30
tsdh joined11:34
OtakuSenpai left11:35
bradleyprice left11:35
esrse left11:36
tsdh Hi. My work repositories are all managed by a GitLab instance that knows my public ssh key and I use repo urls like git@our-server:group/project.git. That works fine when I'm in the company network but not when I connect to the company network via VPN. Then I get: Connection closed by <IP> port 22.11:38
However, telnet our-server 22 shows the same OpenSSH prompt in both situations.11:39
mowcat left11:39
tsdh How can I find the problem?11:39
OtakuSenpai joined11:39
is_null joined11:41
_ikke_ tcpdump, firewall logs11:43
fphilipe_ joined11:45
interrobangd joined11:46
tsdh _ikke_: I think I'll ask an admin. :-)11:47
__Myst__ joined11:57
__Myst__ In a pre-commit hook, is there a way to see only the staged changes?11:57
osse git diff --staged11:57
rsrx left11:57
__Myst__ osse: sorry, i wasn't clear11:58
e.g. say i want to run `tsc --noEmit` on the staged changes11:58
can I run that command on just the staged changes, ignoring the unstaged ones?11:58
osse I don't know what that command does11:58
__Myst__ any command can be subsituted11:58
just saying, can i get the filesystem in a state that's just staged changes?11:59
osse I would suggest you make temporary files in that case11:59
hojang left11:59
Cheaplogic joined12:00
is_null left12:01
ghost43_ghost4312:02
Ayo joined12:02
rosco_y joined12:03
rosco_y what does "git rev-parse origin/master" do?12:04
does it compute a hash every time it's run?12:05
osse __Myst__: i think this will do what you want (or at least do what I want you to want):12:05
Ayo left12:05
bradleyprice joined12:06
osse __Myst__: i think this will do what you want (or at least do what I want you to want): git diff --staged --name-only -z | git checkout-index --temp --stdin -z12:06
__Myst__: this is better (it won't make bogus names):12:09
git diff --staged --name-only -z | git checkout-index --prefix=tmpdir/ --stdin -z12:09
rosco_y If I change my README in github, it doesn't change the hash returned by rev-parse, so I'm confused.12:09
__Myst__ rosco_y: probably need to git fetch first12:09
osse: that's awesome, thank you :D12:09
osse rosco_y: it doesn't compute anything. it just reads the hash of what origin/master points to12:10
__Myst__: I suppose you *can* do it in-place but that would mean temporarily reverting changes to files and restoring them within the hook. That sounds iffu12:10
iffy12:10
bradleyprice left12:11
rosco_y __Myst__, thanks. Please correct me if I'm wrong: I thought git rev-parse origin/master was supposed to return the hash at github, which might not be effected by fetching it to my local repo.12:11
osse !remote_tr > rosco_y12:12
gitinfo [!remote_tracking_branch] Remote-tracking branches (branches which start with e.g. 'origin/', listed by 'git branch -r') are read-only mirrors of the branches in another repository. They're updated by 'git fetch'. You can't edit them directly (trying to check them out results in a !detached HEAD), but you can create a local branch based on a remote-tracking branch using e.g. 'git checkout -b <branch> <remote>/<branch>'12:12
osse rosco_y: very few git commands actually "go online" to get into. fetch and pull do, obviously, and ls-remote. that's the ones I can think of12:12
rosco_y osse, thank! That explains some of my confusion!12:13
_ikke_ (and pull just uses feth)12:13
(fetch)12:13
osse the factoid above is very central to understanding git12:13
_ikke_ git remote as well12:13
rosco_y Thanks __Myst__ , osse et. al.12:13
osse in particular the "read-only mirrors" part :P12:13
rosco_y right. I didn't know anything about those :)12:14
rnsanchez joined12:14
rosco_y sheds new light on 'git fetch' for sure!12:14
subopt joined12:17
BPL left12:19
osse rosco_y: rev-parse is actually very stupid, it turns out12:21
rosco_y: echo 6d96270004515a0486bb7f76196a72b40c55a47f > .git/refs/heads/master12:21
now rev-parse will print that even if it's completely bogus12:21
Amadiro joined12:22
is_null joined12:22
SkarmoutsosV joined12:26
bradleyprice joined12:27
bradleyprice left12:32
kjartan left12:33
kjartan joined12:37
rsrx joined12:37
bradleyprice joined12:48
__Myst__ !detached12:49
gitinfo A detached HEAD (aka "no branch") occurs when your HEAD does not point at a branch. New commits will NOT be added to any branch, and can easily be !lost. This can happen if you a) check out a tag, remote tracking branch, or SHA; or b) if you are in a submodule; or you are in the middle of a c) am or d) rebase that is stuck/conflicted. See !reattach12:49
__Myst__ !lost12:49
gitinfo As long as you have `git commit`ed your changes (or even `git add`ed them), your changes will not be lost for over two weeks unless you work really hard at it. There are two places where "lost" changes can be hiding. They might be in the reflog (`git log -g`) or they might be in lost&found (`git fsck --unreachable`). Type "!dangling" and "!reflog" into IRC for more info.12:49
__Myst__ !dangling12:49
gitinfo Dangling objects represent things added to git which are no longer needed based on the git commands you typed in. This can be normal workflow (rebase, reset, add, etc) or errors you made. Typing "!dangling_commit" "!dangling_blob" and "!dangling_tree" into a query to me will get you more information about each type.12:49
__Myst__ this is a rabbit hole12:49
barteks2x joined12:52
bradleyprice left12:53
_ikke_ haha :D12:57
hojang joined12:59
daggs1 joined13:00
daggs1 Greetings, what is the proper way to get the Author of a commit when executing a pre push hook?13:02
_ikke_ git show -s --format="%an" <commit>13:03
CodeSlingerPaul joined13:04
howell joined13:04
daggs1 _ikke_: thanks, will try it13:05
bradleyprice joined13:06
exitcode1 left13:09
ghoti joined13:09
bradleyprice left13:11
dcpc007 _iike_ thx, user question solved (and more simple in its case : git br -d dev && git br dev :) )13:13
jcbitter left13:14
UrsoBranco joined13:14
_ikke_ dcpc007: git branch -f dev13:14
dcpc007 lol13:15
jcbitter joined13:15
thefatma left13:19
deathwishdave joined13:22
ghoti left13:22
jcbitter left13:23
jcbitter joined13:25
thefatma joined13:25
bradleyprice joined13:28
mat001 joined13:29
jcbitter left13:30
figuinhas joined13:30
jcbitter joined13:31
bradleyprice left13:32
sz0 left13:33
hojang left13:33
dviola joined13:36
deltam left13:36
jcbitter left13:36
jcbitter joined13:37
leb joined13:37
hojang joined13:38
leb left13:40
deltam joined13:41
fflam left13:42
SkarmoutsosV left13:42
fflam joined13:43
tsdh left13:45
is_null left13:47
bradleyprice joined13:49
bradleyprice left13:53
BeerLover left13:57
cdown joined13:57
daggs1 left13:59
bradleyprice joined14:01
Inline joined14:01
bbear joined14:04
bbear hello14:04
It seems I lost some work/commits and I want tot retrive them14:04
How can I do a full text search on most recent commits ?14:04
moritz bbear: it sounds like you really want 'git log -g' or 'git reflog' in the repo where those commits once existed14:05
selckin git log -p -S text14:05
moritz selckin: that won't help if the commits are actually lost :-)14:05
Inline left14:05
moritz might want to add --all14:06
bbear the could not be lost14:06
Inline joined14:07
bbear it's really not possible14:07
m1sosoup joined14:10
bbear I don't manage to do what I need14:10
your commands are grepping commit messages14:11
I want to do a full scan search in the code14:11
or in the diff if you prefer14:11
and preferably have all the refs in my repo in descending order of date.14:11
i'm really frightened14:11
They *must* be somewhere14:11
andrzejv left14:13
comptroller left14:13
bradleyprice left14:13
greggerz joined14:14
bbear that 's not possible14:16
learningc joined14:17
BeerLover joined14:17
cdown left14:19
flaviodesousa joined14:19
BeerLover left14:20
justanotheruser left14:20
bbear okay14:22
so how do I do a full text search in all my commits ?14:22
is_null joined14:23
comptroller joined14:23
Live joined14:27
moldybits left14:28
_ikke_ bbear: commit messages or contents?14:29
SkarmoutsosV joined14:33
is_null left14:36
duderonomy joined14:38
sQVe left14:40
bbear _ikke_: content14:42
is_null joined14:43
nurdie joined14:43
karmenjello joined14:44
mayurvpatil left14:44
karmenjello hello14:44
gitinfo karmenjello: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.14:44
tombusby joined14:45
mayurvpatil joined14:45
rosco_y left14:46
mayurvpatil left14:46
karmenjello if someone creates a pull request, and if merging that pull request would create a merge conflict with another already existing pull request, who's responsible for the merge conflict? In other words, should the second person look at current pull requests to make sure their pull request won't cause merge conflicts before merging their pull request?14:47
Hello71 bbear: man git-log14:47
gitinfo bbear: the git-log manpage is available at https://gitirc.eu/git-log.html14:47
Hello71 karmenjello: depends on the project and the politics14:47
in general the answer is work together14:47
_ikke_ Sometimes it's hard to know there will be a conflict14:48
mase-tech joined14:48
ygivenx joined14:48
_ikke_ like Hello71 said, good communication is key14:49
karmenjello Hello71: thanks for the reply. The project is a shared terraform module. My pull request was already there awaiting 1 more reviewer, and someone else created a different pull request and merged it (they fasttracked it basically by adding reviewers who are known to just click approved without checking it). The actual conflict is tiny, its a matter of principle at this point14:50
mayurvpatil joined14:50
karmenjello mine was the only other pull request14:51
crackin joined14:52
pingo joined14:53
R2robot left14:53
bradleyprice joined14:53
oxymoron93 left14:54
pingo Hi. How do I apply all these feature branches to master branch? https://i.imgur.com/LPdTHZd.png14:54
mayurvpatil left14:56
ryez joined14:56
crackin left14:57
bbear I found it14:57
12ea3db83b9d60cd29531a4756fd49c1a0ef6e5a14:57
but now, I would like to list all the branches where this commit is14:58
how can I do that ?14:58
ryez left14:58
duderonomy left15:00
cybrNaut left15:02
mns I am seeing this when I do a 'git pull': Your configuration specifies to merge with the ref 'refs/heads/branch-of-prod', from the remote, but no such ref was fetched15:02
mayurvpatil joined15:03
mns how do I take care of this ? its not something I've run into before15:03
Noti left15:04
chele left15:05
interrobangd left15:06
bket left15:06
Hello71 left15:06
bluezone joined15:08
thiago joined15:08
neunon left15:08
neunon joined15:08
Lucas_Gray joined15:09
Hello71 joined15:12
queip left15:13
lacrymology left15:14
bket joined15:14
_ikke_ bbear: git branch --contains 12ea3db15:14
fflam left15:16
Hello71 left15:16
fflam joined15:16
cdown joined15:18
AbleBacon joined15:20
is_null left15:21
tang^ joined15:21
Hello71 joined15:22
GreyXor joined15:24
GreyXor Hello, do you know a good best practice git structure ? like a README.md, an /src directory, a LICENSE etc. ? thanks15:25
fphilipe_ left15:25
Hello71 left15:26
hojang left15:26
hojang joined15:27
tang^ GreyXor: that's a decent practice for projects, regardless of which SCM you use15:28
queip joined15:28
mayurvpatil left15:29
hojang left15:32
Hello71 joined15:32
Hello71 left15:32
GyrosGeier in the good old days, our README files were text files15:33
they were not read either15:33
hojang joined15:33
newdimension left15:34
victorqueiroz joined15:34
tang^ they're still text and usually still not read15:35
newdimension joined15:36
orbyt_ joined15:38
is_null joined15:38
cdown left15:38
floppydh left15:38
Hello71 joined15:38
moldybits joined15:39
ygivenx left15:39
Hello71 left15:39
tufteddeer joined15:41
thefatma left15:44
Hello71 joined15:45
oatmealraisin joined15:46
pr0ton joined15:46
Hello71 left15:48
orbyt_ left15:50
oatmealraisin left15:50
oatmealraisin joined15:51
is_null left15:55
mayurvpatil joined15:55
is_null joined15:55
dviola left15:56
Hello71 joined15:56
czart joined15:57
fphilipe_ joined15:57
Hello71 left15:58
mayurvpatil left15:59
hojang left16:02
thiago left16:02
OtakuSenpai left16:02
DisruptiveNL left16:03
Hello71 joined16:04
Hello71 left16:04
davidfetter_work joined16:07
jayjo joined16:08
igemnace left16:10
Hello71 joined16:10
ygivenx joined16:12
AtumT joined16:14
AtumT left16:14
GreyXor left16:14
AtumT joined16:15
fakhraee left16:18
hofmann3900 joined16:19
Hello71 left16:20
GreyXor joined16:25
Hello71 joined16:26
Hello71 left16:27
is_null left16:27
lacrymology joined16:30
m1sosoup left16:32
Hello71 joined16:32
Hello71 left16:33
mowcat joined16:35
pr0ton left16:36
Hello71 joined16:39
bn_work joined16:39
Lucas_Gray left16:39
Hello71 left16:40
lacrymology left16:41
Enphuego joined16:42
lacrymology joined16:43
kjartan left16:44
thiago joined16:45
Lucas_Gray joined16:45
Hello71 joined16:45
Hello71 left16:46
Shentino left16:47
oatmealraisin left16:47
mikecmpbll left16:49
kjartan joined16:49
oatmealraisin joined16:49
Shentino joined16:50
Mike11 left16:51
Hello71 joined16:51
tufteddeer left16:52
Hello71 left16:52
impermanence joined16:52
tufteddeer joined16:53
impermanence left16:55
is_null joined16:56
impermanence joined16:57
tufteddeer left16:58
Hello71 joined16:58
tufteddeer joined17:00
flaviodesousa left17:01
Hello71 left17:01
Newami joined17:01
duderonomy joined17:01
Hello71 joined17:07
barteks2x left17:07
barteks2x joined17:08
Hello71 left17:08
acercle joined17:13
Hello71 joined17:14
jab416171 joined17:15
fstd_ joined17:16
Hello71 left17:17
Jitta joined17:17
rsrx left17:19
fstd left17:21
fstd_fstd17:21
plexigras joined17:22
rsrx joined17:23
Hello71 joined17:23
figuinhas left17:26
queip left17:27
nowhere_man joined17:31
Hello71 left17:33
Lucas_Gray left17:33
mowcat left17:35
tufteddeer left17:35
figuinhas joined17:36
tufteddeer joined17:37
figuinhas left17:37
queip joined17:37
T_UNIX left17:38
Hello71 joined17:39
Hello71 left17:40
Lucas_Gray joined17:40
maarhart_ joined17:40
maarhart_ left17:40
maarhart_ joined17:41
maarhart_ left17:41
maarhart_ joined17:41
maarhart_ left17:41
maarhart_ joined17:41
GreyXor left17:42
freeman42x joined17:43
maarhart_ left17:44
Hello71 joined17:45
JoaTMoN joined17:46
Hello71 left17:46
queip left17:47
Lucas_Gray left17:48
deathwishdave left17:49
JoaTMoN left17:50
orbyt_ joined17:53
queip joined17:53
Hello71 joined17:54
Hello71 left17:55
Narrat joined17:56
Hello71 joined18:01
plexigras left18:01
Hello71 left18:02
karmenjello left18:04
pingo left18:07
infernix left18:07
Hello71 joined18:08
plexigras joined18:09
alyptik left18:09
czart_ joined18:09
czart left18:10
leeN joined18:13
Hello71 left18:18
bbear left18:19
learningc left18:22
wootehfoot joined18:23
Hello71 joined18:24
Hello71 left18:25
is_null left18:28
is_null joined18:28
sauvin left18:29
Hello71 joined18:31
subopt left18:32
lacrymology left18:33
clime left18:34
Hello71 left18:41
clime joined18:42
is_null left18:44
Hello71 joined18:46
infernix joined18:47
Hello71 left18:47
slacker_nl perhaps we should name them IGNOREME18:48
pyfgcr left18:49
R2robot joined18:51
smitop joined18:51
lss8 left18:52
Hello71 joined18:53
Hello71 left18:55
jesopo left18:55
moritz SECRETS_DONT_READ18:57
ChanServ set mode: +o18:59
ChanServ set mode: -o19:00
Hello71 joined19:00
Hello71 left19:02
is_null joined19:06
impermanence left19:07
Hello71 joined19:07
is_null left19:07
infernix left19:09
jenia joined19:11
jenia hello19:11
I need to revert all the change from HEAD all the way to commit xyz19:11
when I do git revert xyz nothing happens at all19:11
vishal !revert19:11
gitinfo That's a rather ambiguous question... options: a) make a commit that "undoes" the effects of an earlier commit [man git-revert]; b) discard uncommitted changes in the working tree [git reset --hard]; c) undo committing [git reset --soft HEAD^]; d) restore staged versions of files [git checkout -p]; e) move the current branch to a different point(possibly losing commits)[git reset --hard $COMMIT]?19:11
vishal also, potentially, !rewrite applies19:12
gitinfo Rewriting public history is not recommended. Everyone who has pulled the old history will have to do work (and you'll have to tell them to), so it's infinitely better to just move on. If you must, you can use `git push --force-with-lease <remote> <branch>` to force (and the remote may reject that, anyway). See http://goo.gl/waqum19:12
Mattiaslndstrm left19:12
jenia vishal: is it a new program called git-revert or there's a submodule in git called `git revert...`19:12
?19:12
oatmealraisin left19:13
inkbottle left19:13
vishal git revert is part of git, but it sounds you might want reset rather than revert (with the rewriting caveat)19:13
jenia vishal: no. I want to make a new commit that does that opposite of the commits from xyz to HEAD19:14
inkbottle joined19:14
vishal ah, ok, then you want to specify a range to revert, not just 'xyz'19:15
perhaps git revert xyz..HEAD19:15
!dots19:15
gitinfo A..B = stuff that happened between A and B (if A and B are related; otherwise refer to "man gitrevisions"), A...B = (a) in history viewers: stuff that isn't in both A and B yet; (b) in "git diff": stuff that happened in B since the two diverged; (c) in "git checkout": the merge base of A and B. "master.." is the same as "master..HEAD" and "..master" is the same as "HEAD..master", and so forth.19:15
jenia vishal: well yes. so git revert head..xyz. But I need HEAD to be undone to19:16
Hello71 left19:17
jesopo joined19:19
bradleyprice left19:19
jenia f*** I'm getting empty commit set passed. I did `git revert abc..xyz` where abc is HEAD19:20
vishal you want xyz..HEAD not the other way round19:20
infernix joined19:23
Hello71 joined19:23
hojang joined19:23
Hello71 left19:27
plexigras left19:28
bradleyprice joined19:29
alyptik joined19:30
jcbitter left19:31
jcbitter joined19:32
Cheaplogic left19:35
xelxebar left19:35
xelxebar joined19:35
Cheaplogic joined19:36
emsjessec left19:36
jcbitter left19:38
jcbitter joined19:39
deathwishdave joined19:40
Sasazuka joined19:40
Hello71 joined19:42
deathwishdave left19:43
xorander left19:44
n3wborn joined19:45
czart_ left19:47
jwynn6 left19:47
fphilipe_ left19:47
jwynn6 joined19:48
xorander joined19:50
gloomy left19:50
wreed joined19:51
im0nde- joined19:51
VectorX left19:54
im0nde| joined19:54
im0nde_ left19:54
im0nde left19:55
ricekrispie left19:58
Nickeeh left19:58
MACscr_ joined20:02
VectorX joined20:02
paws_ left20:03
MACscr left20:04
im0nde-im0nde20:04
cd left20:06
APic joined20:06
sgen joined20:06
ricekrispie joined20:16
bradleyprice left20:17
bradleyprice joined20:17
jayjo left20:18
learningc joined20:22
bradleyprice left20:22
bradleyprice joined20:24
crackin joined20:25
plexigras joined20:26
mojisun joined20:27
inovas left20:29
inovas joined20:30
jayjo joined20:30
crackin left20:30
jayjo left20:33
theoceaniscool joined20:43
greatgatsby joined20:43
mojisun left20:46
wreed left20:47
averell joined20:48
salad left20:51
mowcat joined20:53
Lucas_Gray joined20:59
paraxial joined21:00
R2robot left21:08
queip left21:09
rsrx left21:11
mase-tech left21:16
R2robot joined21:17
Unplesantry joined21:17
Unplesantry any way to clone a repo in bitbucket like create a new one from another21:18
_ikke_ Unplesantry: you can do it locally21:19
oatmealraisin joined21:19
_ikke_ create a new project in bitbucket, then add the project as a remote to your local repo and push to tit21:20
to it*21:20
Jitta left21:20
Unplesantry ya i know that21:20
nowhere_man left21:20
Unplesantry i wish they make a button for that already21:20
create from existing21:21
nurdie_ joined21:21
justanotheruser joined21:23
vishal Like a fork button? (I don't use bitbucket)21:23
Unplesantry ya i guess that is a fork21:23
duh21:23
_ikke_ a fork is not independent though21:24
queip joined21:24
nurdie left21:24
Nickeeh joined21:25
nurdie_ left21:25
Unplesantry oh21:27
Narrat left21:28
wootehfoot left21:32
jayjo joined21:34
bradleyprice left21:39
bradleyprice joined21:39
mns left21:40
mns joined21:41
Anticom joined21:43
foul_owl left21:44
bradleyprice left21:44
AbleBacon left21:44
Anticom left21:44
crackin joined21:45
howell left21:46
hojang left21:47
rustyshackleford joined21:49
crackin left21:50
queip left21:50
paraxial left21:52
Rhonda left21:54
mns left21:54
sgnls left21:54
paraxial joined21:55
plexigras left21:55
tufteddeer left21:55
Rhonda joined21:55
mns joined21:57
greggerz left21:59
foul_owl joined22:00
queip joined22:00
AtumT left22:05
matheusmoreira left22:05
sgen left22:06
strudla left22:07
strudla joined22:07
AtumT joined22:08
sgen joined22:11
matheusmoreira joined22:11
nowhere_man joined22:13
AtumT left22:16
clime left22:17
crackin joined22:17
jklaus joined22:17
jklaus hey guys, I need some help with gitversion gitflow if at all possible22:18
bradleyprice joined22:20
moei left22:20
crackin left22:22
jklaus can anyone tell me why this daygone thing doesn't work22:23
CodeSlingerPaul left22:23
bradleyprice left22:24
lungaro joined22:24
lungaro is there a way to specify what ssh keys should be presented for a given git repo?22:25
Its about time I try to fix this. I used to just load the key into my agent that I needed and unload the others. I have multiple ssh identities on github.com and its getting them wrong22:25
jklaus @lungaro - are you familiar with gitflow?22:26
lungaro Nope22:26
bashfulshell left22:28
vishal lungaro: you can do it by manipulating your remote config for the repo and your .ssh/config to specify keys for those remote-aliases22:30
lungaro ok22:31
vishal e.g. remote url would be ssh://identity1/org/repo.git and ssh config would have a Host identity1 section specifying the hostname and key22:32
lungaro cheers22:33
nasamuffin left22:34
leeN left22:36
thiago left22:36
learningc left22:38
zlogan2003 left22:38
jklaus anyone know how I can migrate the version from my source branch to become a tag on my target branch during a merge (specifically a pull request in ADO)22:38
queip left22:39
nasamuffin joined22:39
galaxie joined22:40
galaxie left22:42
vishal jklaus: I don't fully understand - If you want a tag, you have to create and push a tag. Also what's an ADO?22:44
jklaus vishal - I'd prefer to stay away from tagging22:45
I'd rather use branch naming of say a hotfix or feature branch22:45
queip joined22:45
jklaus but I want it to carry from said feature up to develop22:45
the version that is.. I think I may have figured out how22:46
SkarmoutsosV left22:46
jklaus In the gitversion.yml I think I may be able to specify the major, minor, patch via the mergeVersion22:47
SkarmoutsosV joined22:47
jklaus I'm essentially looking at using branching as the way of controlling pre-release vs release22:47
for nuget packaging22:47
SkarmoutsosV left22:48
SkarmoutsosV joined22:49
bn_work left22:51
theoceaniscool left22:52
davidfetter_work left22:53
nic-hartley joined22:59
tang^ left23:00
dre_ joined23:01
kjartan left23:02
oatmealraisin left23:02
acercle left23:05
kjartan joined23:06
n3wborn left23:08
Lucas_Gray left23:08
smitop left23:11
raedah joined23:12
foul_owl left23:14
LionsMane left23:15
sgen left23:18
wreed joined23:20
seebyr joined23:22
yonder joined23:24
dre_ left23:24
seebyr left23:25
sbeyer left23:26
foul_owl joined23:27
moldybits left23:28
bradleyprice joined23:34
dege left23:36
bradleyprice left23:38
duderonomy left23:38
sozuba left23:41
sgen joined23:42
Cabanossi left23:45
infernix left23:45
khisanth_ left23:46
lungaro left23:46
bluezone left23:47
hio left23:50
Cabanossi joined23:51
wreed left23:53
queip left23:53
R2robot jklaus: https://nvie.com/posts/a-successful-git-branching-model/ is what I use23:54
jklaus R2robot - I'm not seeing a way I can carry a version stamp from say a release branch into a develop23:58
bradleyprice joined23:58
bradleyprice left23:58
jklaus ie, I want to set the version by creating a release branch called releases/2.0.023:58
when that PRs into develop I want develop to get tagged 2.0.023:58
R2robot merge then tag?23:59
are you working solo?23:59
but why do you want to tag develop?23:59

Logs Search ←Prev date Next date→ Channels Documentation