git workflow
git workflow
39 comments
-
Be a man.
‘git commit -am “changes”’
-
At this point just create a script or alias called "fuckthis" that does that and then push direct to main
-
PR reviews take the most time, eliminating those saved us loads of time.
QA were also bogging us down, axed them too. Now we’re flying.
The Social Security Infrastructure rebuild should be done in a matter of weeks! At least that’s what Copilot says.
-
I have auto save on. A cron job running every minute with just git add . && git commit - m "wip"
-
Have the name of the alias be "gti" or "gut"
-
-
And any project worth their salt will reject it for two reasons:
- Unclear message/changes (potentially too many changes at once)
- Not signed
-
I’ve got signing auto enabled though
-
Doesn't work for me idk why, it'll ignore the message, and i have to commit again before i can push
-
-
... What's
git mergelook like?-
Tenerife incident.
-
... incident
-
-
-
grow up, use "git add -p" and craft perfect artisanal commits
-
Real 10x vibe developers use https://jj-vcs.github.io/jj/latest/, no need to add or commit!
-
i'm sure there are much better tools available, but i'm just used to git gui where rescan, commit and push all are in order.
-
Every bloody time, though this case the people not on the Ryanair flight may be the lucky ones. If only git was the most unnecessarily arcane thing devs have to/choose to work with.
-
Use Jujutsu
jjand you won't have this problem
-
lazygitis pretty cool too.
-
I specifically have a oh-shit alias for this kind of stuff lol: https://code.wedotstud.io/patrick/dotfiles/src/commit/c2f93629fe27d1747ceb22b4d6442840d109aa99/.gitconfig#L28
-
I set this up for seamless commits:
function gao() { git add . git commit -a -m "$*" git push origin `git rev-parse --abbrev-ref HEAD` }Usage: gao fixing a typo
-
Jujutsu time 😁
39 comments