>tfw finally pushed that big commit
Tfw finally pushed that big commit
Jacob Perry
Other urls found in this thread:
git.kernel.org
twitter.com
Jonathan Perez
>at job interview
>company doesn't use git
Jackson Hall
Please do not give cats coffee.
Jeremiah Stewart
i-it's cocoa
Jose Collins
What did you commit to?
I recently committed to my gf and to using Linux purely as my daily driver rather than dual booting. Is this a commitment thread?
Liam Long
>pushing a big commit
user, commits should be small. You should always be pushing small bits of code so you can always go back to it later.
Jayden Scott
I don't like pushing unfinished features.
Adam Harris
>tfw finally did something for the first time worthwhile on github
>I found a specific bug/ dev fuck up and posted a work around and a solution
I finally helped the open source community guys. It only took me 10 years
David Robinson
That is why you fork and merge, my dude.
Kevin Sanders
Ugh. When I have a feature branch thats more than a few days old I start to get anxious. You just know merging is going to be fucked and you're going to have to hound someone so hard for a code review
Robert Davis
Having large features could be a symptom of bad design.
Jack Edwards
Too complicated
Jason Edwards
rebase every now and then? whats the problem?
Parker Martin
>he makes his commit messages in the form of >"____ed the ____"
>"_____ed bug"
>"___ed"
every other commit message that is autogenerated from git is in the present tense
why would you voluntarily be inconsistent.
git.kernel.org
Jack Harris
When the branch has too much in it, and you need a code review to get it into the main branch, and in the time it takes to get reviewed someone else commits something that conflicts, which resets the whole process
Henry Flores
He commited his code changes to a repository, not made some life commitment.
Lincoln Hall
Really? It would seem to me that on such a small time scale conflicts would be trivial to solve, and not require another review
Elijah Garcia
>tfw finally took that big shit
Samuel Martinez
Depends on the project, the architecture, the state of development, and the discipline of the team.
Wyatt Turner
>I can only use git
>too stupid to learn anythin else
>spend days on Jow Forums
>mock imaginary company for using something else than git
Fosil, mercurial... even svn is not that bad. No need to go full "muh git"
Jace Phillips
99.9% of the time if a company isn't using git, they're using the "copy the directory and merge by hand" method. That's what user was referring to.
Jack Thomas
>I can only use git
Wrong.
>too stupid to learn anythin else
Wrong.
>spend days on Jow Forums
True.
>mock imaginary company for using something else than git
I've had it happen.
>Fosil, mercurial... even svn is not that bad.
You're even admitting they are all worse than git.