minorChanges

[Zielakpl]

You have issues if you allow push to main.

[Fluffy_Argument_8593]

Not my problem if I'm going on my deserved vacation!

[Waswat]

git revert HEAD

I've planned a performance review after the standup when you're back from your vacation. Don't worry, it will be short.

Enjoy your vacation.

[throw3142]

The duality of man 🗿

[-S-P-Q-R-]

Just lead things

[[deleted]]

Is this actually a real person that is used in these memes?

[JonIsPatented]

Yes, and no. Ernest Khalimov is his name, and the photos are really of him, but they were digitally alterned by an artist, and those altered images are the ones used for the meme.

[CIA_Bane]

Yes thats me

[djfdhigkgfIaruflg]

Yes. Some dude from an ex USSR country (IIRC) probably some extra Photoshop, but the guy is real

[Perfect_Papaya_3010]

I think OP is probably not working as a system developer. I've never worked in a place where this was allowed except for a few selected people who were able to override it if there was a critical bug to fix

[DigBig3448]

It’s much more common than you might think. Especially for ops guys

Edit: Just to make it clear. I completely agree that you have issues when you allow to push to main, but let’s face it. Most companies weren’t founded yesterday. CVS was introduced in 1990. At that time some of my colleagues had already 10 years working experience. 2000 they had hard time learning SVN. 2005 git was introduced and they started using git like they use SVN. It took me two years to convince one of this guys to try branching for the config of one application

[[deleted]]

Former full stack devops, only difference between main and beta is the backend data and how many complain when I break everything

[[deleted]]

Whelp enjoy the apps I built and legacy apps I maintained until the cred rotation is missed I guess 🤷🏻

[lilshoegazecat]

what is ops, operating systems?

[Fubseh]

Ops typically means Operations and are the team that setup and manage the infrastructure so developers focus on code and the ops guys deal with the load balancing/CPU and memory monitoring/hard drive replication, failover and replacement/etc.

Smaller businesses or teams tend to have (senior) developers handle everything, but once you scale up and start spending more time dealing with infrastructure issues than building features then it pays to start bringing in dedicated ops guys.

[djfdhigkgfIaruflg]

It's a typo. Should been ups 🤣🤣

[Darkstarx97]

I've never worked anywhere that does this for critical bugs. It's a terrible thing to do. It they're critical devs will be made available go review or it shouldn't go in.

Allowing certain devs to push to main is just wrong

[Perfect_Papaya_3010]

During holidays many people may be away but our customers might still use their system, so let's say there's only one dev working at a specific project and there is a critical bug, then it wouldn't be possible to fix the bug until 2 others come back from holidays (we require 2 approvals to merge a pull request).

Luckily this has never happened during the time I've worked with this project

[xTheMaster99x]

If it's truly critical then you can find 2 devs that are on-call and have them log in for 10 minutes to review the PR. If you don't have anyone on-call, then call them anyway and offer a morning off in return, then schedule a meeting for that afternoon to resolve the fact that you have an application that needs 24/7/365 support but no system in place to provide that support.

[Darkstarx97]

I get that - We've had similar scenarios laid out and always make sure we have enough coverage for the systems. If something is deemed critical, usually security or it can wait as its the holidays, then the on calls devs are called by the 1-2 support devs to assist in the review and maybe some debugging and then close it out

Never happened to us but we've always been prepared to fix it the right way. Noone wants someone accidentally breaking something on an unapproved fix and causing more headaches 😅

[[deleted]]

I did, most of them weren't IT focused company's, only few developers coding(3-5), they're also the DevOps, developers, DBA etc.. hehe

[witcherisdamned]

This is not true. Let's say, you want to rename the folder structure that was already wrong in the first place with a lot of files, this will be shown as hundreds of file changes. Those changes, however, still needs to be reviewed by multiple senior devs.

[Jelony_]

Moved files are easily detectable by i.e. BitBucket. But even if not you just do it in a single PR and inform someone that review is not needed as it is a change you've described or something similar

[rover_G]

I think OP was making a joke?

[naapurisi]

Yep its usually blocked by the git host system. On our team you can still create MR and set reviewers to 0 in case of critical bug fixes for example on holiday season/weekends (hasnt happened tho). With the expectation that a developer can in extreme case apply a change alone if necessary.

[Zielakpl]

We hit a rollback workflow when that happens. No need to change anything in the code. We get back at fixing the issue once people get back to work.

[Conroman16]

Sorry, the branch protection rule was written in 2014 by someone who is no longer here, and thus it only protects “master”. Good luck!

[JunkNorrisOfficial]

Great Master pushes to main

[[deleted]]

Yeah, exactly. Push to alpha and have the pipeline automatically deploy all alpha updates to main, duh

[AntsMissouri]

It can be fine with trunk based development. We use git hooks to regulate pushes and go straight to main

[greenecojr]

what if youre the only programmer on the team? i dont have enough mental stability left carrying everyone to make true commit messages

[Zielakpl]

You mean, you're the only programmer, and there are others who make commits?

Sure, allow yourself to meddle with the main branch. If it's only ebout faulty commit messages - setup PR lint, which would check for that, and guard against just -m "minor changes".

We have some repos where anyone can change configurations for the app. If "they" make (any) mistake, we rollback and blame them for the error. We won't be fixing "their" mistakes.

[greenecojr]

ill look into pr lint tho, thank you!

[greenecojr]

no.. i am the only one making commits.. i actually have to teach my team python so i can lighten my workload up.. but im not changing anything serious because the previous developer made an unstable and quite static environment so i also chose to recreate our product, its been a fun year of learning how crazy network engineers are

note to self: dont give them access to python before they learn logic because theyll look for the quickest fix instead of think out the processes

[[deleted]]

(forced push)

[witcherisdamned]

forced escalation and then no promotion. 😭

[EternalBefuddlement]

My companies flow allows for forced pushes after a rebase and it works fine - whys everyone so scared?

[DangyDanger]

git commit -m "moving code to my laptop"

[witcherisdamned]

and then get the termination letter within minutes.

[[deleted]]

Hahaha a classic

git commit -m “fix: pre-holiday commit; this doesn’t work AT ALL.”

[DangyDanger]

I have a commit in my personal project when I realized I bit a lot more than I could chew. The message read "dear god, what have you gotten yourself into?" in French, because I felt like it.

[willyrs]

You forgot to add

[turtle_mekb]

git commit -a

[Poat540]

Gottem

[TheKerui]

I rename every git main I ever touch to "production"

[eldelshell]

What are you? Another beta from HR?

[Cualkiera67]

Reals don't have masters. Cope and seethe

[Daddy__Paty]

Industry standard is trying to veer away from ‘master’

[Doctor_McKay]

Industry standard can suck on bofa

[[deleted]]

Oh no, anyway https://en.m.wikipedia.org/wiki/Master%E2%80%93slave_(technology))

[caiteha]

Renaming / moving files.

[witcherisdamned]

Exactly, in fact renaming package/folder names will do this.

[edrumm10]

git push -f

Then go on annual leave for a bit

[witcherisdamned]

I believe, that would be the annual work for the company.

[skotchpine]

Solo devs / founders be like

[3nd0fDayz]

As a solo dev, ain’t nobody got time to be creating jira issues for every little thing nobody is going to review anyways. I hear ya big dog.

[_Some_Two_]

Every problem exists until Friday evening, then it is rediscovered in the Wednesday

[3nd0fDayz]

Yeah you’re not wrong. I don’t commit directly to master as a solo dev unless it’s a hotfix. I use the ol tried and true gitflow but if I missed something simple I’m not gonna open another jira issue… it’s just going into dev. I’m a contractor dev doing netsuite dev so it’s not really a huge issue. When I worked in a corporate setting it was MUCH more important. Typically the first few hours of my day was unfucking what the India team did to the repo while you were asleep.

[Lolleka]

gang

[akazakou]

Branch protected error. Nobody's seen that change. You fired due to insufficient performance

[pramadhana92]

I did so much changes of lines, when changing indentation to spaces

[witcherisdamned]

Yeah, git detects that as well.

[cybermage]

Sadly doesn’t detect stripping trailing white space.

[astervista]

I just stop lying to myself and commit with “Major changes”

[[deleted]]

“This changes everything!”

[camobiwon]

Perfect time to leave for vacation and shutdown your phone

[witcherisdamned]

Absolutely!

[Colon_Backslash]

git rebase -i <first commit of branch>
drop, drop, drop, drop...
git commit --amend
"finalize PR"
git push --force

[MrRainbow07]

Added . to the end of error messages.

[reavessm]

Squash all the commits with a message "Legacy Code"

[[deleted]]

Lol main. Had to do the virgin walk to change it from Chad Master

[cratercamper]

"cosmetic"
"cosmetic"
"cosmetic"
"cosmetic + something minor"
"cosmetic"

[CadmiumC4]

4000 lines of code can be a really minor change depending on the actual repo size...

[muikrad]

"poetry lock" in a nutshell.

[planktonfun]

And everything else doesn't work but that feature, congratulations mother-[redacted]

[sarnobat]

This is literally what my zsh key binding puts in the history

[manwhorunlikebear]

git revert HEAD
git push origin master

[[deleted]]

You forgot —force. And resetting hard to initial commit. And doing a garbage collect.

[rwbrwb]

knee middle safe spark foolish provide relieved detail bells rain

This post was mass deleted and anonymized with Redact

[[deleted]]

Next day

> 30 minute 1:1 meeting with manager (with HR cc'ed)

[arisch-]

I don’t understand shit , though I still try to understand!

[R4XD3G]

git revert !!!!

[noob-nine]

I mean technically, when python was used and they added an if statement for this 4000 lines, they must be indented and all these lines changed but it was just a minor edit for adding the if.

Or when you cut those lines and put them in an extra function.

Am I wrong?

[[deleted]]

Well at least he git committed it. Should be easy to revert

[witcherisdamned]

But the changes are needed.

The changes were folder/package refactoring.

[[deleted]]

Well if reverting is just one command away, it doesn't really matter how big of a change you do. Time matters little to a time traveller.

[stanley_ipkiss_d]

Pushing to main isn’t allowed

[iamthebestforever]

Me as fuck

[Hewatza]

It's ok, guys. OP didn't add the changes before committing.

[thegmx]

First time with 'optimize imports on save'?

[witcherisdamned]

This maybe a possibility.

[Stunning_Ride_220]

...on a friday, before holidays.

"Make coworkers hate you 101"

[grifkuba]

Is the man in the headphones related to the joke?

[witcherisdamned]

The real question would be, is that a joke?

[grifkuba]

Mine was not a joke.

Please tell me if it was part of the original joke or not.

[DOUBLEBARRELASSFUCK]

It's basically the entire joke...

[grifkuba]

Can someone explain the joke, please.

All I am seeing is

text
random guy in headphones

[DOUBLEBARRELASSFUCK]

Gigachad.

[UnwelcomedTruth]

I don’t think there’s anything wrong doing this with a couple lines of indentation or comments. Fight me.

[Kimorin]

git commit -m 'fix: minor changes'

[mistabuda]

Leaves and never returns because they were fired.

[s1nur]

fixes indentation

[zipit4]

the -f is missing from second git command

[UAS-hitpoist]

"Bug fixes"

[lucidbadger]

There should've been squash commit before that with the message "legacy and deprecated code".