- 16 hours
well yeah, in an enterprise project we would say “chore(test)”. Semantic release ftw!
- tdgoodman@lemmy.dbzer0.comEnglish20 hours
I cannot give you a 100% for consistency. You have three inconsistent check in messages: ‘tet’, ‘FueraEstanciaRowRename’, and ‘Revert “test”’. You must be uniformly informative with your messages.
You don’t just write your entire project, then make your first commit?
/j
I do kinda do that with the initial commit (don’t commit anything until I have something really basic that works). It feels awkward to commit code that does nothing.
Seriously. My colleague does the same shit and it made me so mad until I realised he was on his branch. Then I was like, whatever, as long as you do a proper MR.
- 7 hours
git commit --amend --no-editandgit push --force-with-leaseNo-edit skips opening an editor for the commit message and just reuses the same message.
Force-with-lease will force push but only if your local is not missing commits that remote has. Ie other people haven’t pushed anything since you last pulled.
- 13 hours
If you’re comfortable with whatever text editor vim uses, give git rebase -i a try.
- 1 day
Would this also trigger (
git rev-parse) to change? I have CI/CD listening to changes on the master branch- 1 day
When you have to amend a commit that you have already pushed you have to force push the amendment. That should then trigger the Pipeline
–force-with-lease though, not just force… It’s a good habit to have because then when you are working with other people you won’t fuck everything up.
- 1 day
This is good advice, I got too used to being a solo dev that once I worked with a larger team… mistakes were made.
Work off the master branch first, don’t push to prod until you’re ready to
- 1 day
Well, prod is luckily the people I have next room. I made the setup so changes get uploaded quickly. I could do branches and all that stuff?
Yeah, but i’d rather not work to work and just get it out the door. What my setup is for is that changes get pulled off the master branch and deployed without an apparent interruption of service.
I see collaboration tools just the same as abstractions, you don’t use them just to use them. They need to solve a problem.
- 1 day
It’s a collaboration tool and i’m not collaborating with anyone so why’d I bother going through the extra bells and whistles?
VCS’s are organizational tools as much as they are collaboration tools. You should learn it and use it to improve your coding abilities through better management.
- VibeSurgeon@piefed.socialEnglish1 day
Well, there’s your problem.
Get yourself a nice button/endpoint you can hit to trigger CI/CD that way instead
- 1 day
You’re saying it’s a problem but i’m not really reading why. While the idea of a massive button to push changes is fun having the master branch be production is a concrete idea i’ve grown fond of, iteration is fast, both at testing and deployment.
- 1 day
Has your real dev commits gotten you a real dev job? You seem to be looking for a job offer on your mastodon since february and i’m worried for you.
- bss03@infosec.pubEnglish20 hours
I’m not sure if any of those commits did, but I worked 2 years doing Haskell backend and jQuery+Bootstrap frontend for Masterword. Before that I did some work for Wire: https://github.com/wireapp/wire-server/commits?author=stephen-smith Before that, I worked at TGCS for nearly a decade.
But, right now I am still looking for work. I’ve actually been looking since April 2025 when my time at Masterword ended, but I did update my “hire me” posts back in February because my living situation changed, opening up more opportunities. Originally I needed something remote so I could continue to take care of my father (RIP), now relocation is certainly an option.
If anyone reading this has a position available, or is just curios, my current resume public: https://docs.google.com/document/d/1ORf48b557nK0gYI4h6J0xP7nzOVRoqtOogYsukUMREU
- Jerkface (any/all)@lemmy.caEnglish1 day
I love editing history. Fix the bug in the change that introduced it!
1 daygit branches are free
work in your tree
til the changes are ready
300git push --force-with-leasea day and nobody madNothing about continuous integration prevents you from using a branch to prepare your changes.
- 1 day
Yes, if you use feature branches its literally not continuous. It’s adjacent though.
Continuous Integration is a software development practice where each member of a team merges their changes into a codebase together with their colleagues changes at least daily
Meaning everything is in a version controlled mainline
People disagree about what CI is, but that’s the definition i subscribe to
So does everyone work directly on main all the time? Do all of you work on the same project or are there multiple with one person per project? How do you work around the broken code your coworker just pushed so you can finish your tasks?
- 1 day
I prefer to force push directly to the production branch.
- 1 day
I personally don’t really care for the meaningful messages or a pretty log. I only see these myself.
- Jerkface (any/all)@lemmy.caEnglish1 day
And clearly as a Windows developer, you hate yourself and don’t believe you deserve nice things, so it all checks out.
- Jerkface (any/all)@lemmy.caEnglish1 day
This is just your self-hatred turned outwards. I forgive you.
I’m very confused haha. didn’t you say this code was just personal code? or that it was just for yourself? If you’re at a job why are you committing like this?
in any case, I’m sorry for the absolute crazy amounts of hate you’re getting for using windows. I do highly recommend trying out linux though. unless you’re doing cad or 3d modeling, you will likely have zero issue using it.
- 1 day
I’m the only programmer at the company. It’s a closed source solution for very specific needs. So I only answer to myself and I don’t have a need to explain (to myself) what I did in a particular commit and if I ever need to check the commit history I can just check a particular files history, not going commit by commit. I never said it was personal code. I said “don’t code alone”. I use linux at home, the server hosting the code commits is linux, the scripts listening to new commits are in bash.
- 7 hours
Whoever works that job after you leave is going to curse your family lol. That’s wild to think like that.
With my salary, I am boss of my OS. I tell my boss, “you really want me working on that pile of shit? Okay, it’s your time.”
- 1 day
I didn’t make this post to defend someone elses decision and all this thread is doing is assume shit because I got to use windows. Yes, composer takes ages to optimize the autoloads on windows. I know.
You’re all just being insufferable to someone forced to use it.
- Jerkface (any/all)@lemmy.caEnglish1 day
I mean if you’re taking it this seriously, it was probably way more on the nose than I realized when I just intended it to be silly.
- 1 day
Should I find a problem solved by me adding commit messages i’ll gladly do it. I use stuff as I find an usecase for it. Atm, i’m completely alone so i’ve 0 need to write up what my changes do. It personally gets in the way of quickly iterating and then testing.
- 1 day
Then why are you using source control at all? You can manually copy the directory and name it “— Copy”.
then just always force push. You’re not even using the source control, you might as well just use a shell script to deploy rather than listening on CI/CD
- copacetic@discuss.tchncs.deEnglish1 day
Looks like a normal branch where someone debugs some GitHub workflow.
- 1 day
More like laughs out of relatability. Tho I am getting dogpiled for the industry standard practice of using what the company provides.
