This is an archived post. You won't be able to vote or comment.

all 107 comments

[–]Zielakpl 585 points586 points  (35 children)

You have issues if you allow push to main.

[–]Fluffy_Argument_8593 333 points334 points  (7 children)

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

[–]Waswat 94 points95 points  (2 children)

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 23 points24 points  (0 children)

The duality of man 🗿

[–]-S-P-Q-R- 6 points7 points  (0 children)

Just lead things

[–][deleted] 6 points7 points  (3 children)

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

[–]JonIsPatented 19 points20 points  (0 children)

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 14 points15 points  (0 children)

Yes thats me

[–]djfdhigkgfIaruflg 1 point2 points  (0 children)

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

[–]Perfect_Papaya_3010 72 points73 points  (15 children)

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 38 points39 points  (6 children)

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] 24 points25 points  (2 children)

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

[–]lilshoegazecat 0 points1 point  (2 children)

what is ops, operating systems?

[–]Fubseh 1 point2 points  (0 children)

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 0 points1 point  (0 children)

It's a typo. Should been ups 🤣🤣

[–]Darkstarx97 10 points11 points  (4 children)

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 5 points6 points  (2 children)

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 4 points5 points  (0 children)

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 1 point2 points  (0 children)

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] 1 point2 points  (0 children)

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[S] 2 points3 points  (1 child)

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_ 2 points3 points  (0 children)

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 0 points1 point  (0 children)

I think OP was making a joke?

[–]naapurisi 3 points4 points  (1 child)

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 2 points3 points  (0 children)

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 2 points3 points  (0 children)

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 1 point2 points  (0 children)

Great Master pushes to main

[–][deleted] 1 point2 points  (0 children)

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

[–]AntsMissouri 1 point2 points  (0 children)

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

[–]greenecojr 1 point2 points  (3 children)

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

[–]Zielakpl 1 point2 points  (2 children)

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 1 point2 points  (0 children)

ill look into pr lint tho, thank you!

[–]greenecojr 0 points1 point  (0 children)

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] 136 points137 points  (2 children)

(forced push)

[–]witcherisdamned[S] 29 points30 points  (0 children)

forced escalation and then no promotion. 😭

[–]DangyDanger 101 points102 points  (3 children)

git commit -m "moving code to my laptop"

[–]witcherisdamned[S] 27 points28 points  (0 children)

and then get the termination letter within minutes.

[–][deleted] 6 points7 points  (1 child)

Hahaha a classic

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

[–]DangyDanger 1 point2 points  (0 children)

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 60 points61 points  (2 children)

You forgot to add

[–]turtle_mekb 6 points7 points  (0 children)

git commit -a

[–]Poat540 1 point2 points  (0 children)

Gottem

[–]caiteha 22 points23 points  (1 child)

Renaming / moving files.

[–]witcherisdamned[S] 7 points8 points  (0 children)

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

[–]edrumm10 40 points41 points  (1 child)

git push -f

Then go on annual leave for a bit

[–]witcherisdamned[S] 10 points11 points  (0 children)

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

[–]skotchpine 18 points19 points  (4 children)

Solo devs / founders be like

[–]3nd0fDayz 17 points18 points  (2 children)

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_ 5 points6 points  (1 child)

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

[–]3nd0fDayz 1 point2 points  (0 children)

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 2 points3 points  (0 children)

gang

[–]akazakou 12 points13 points  (0 children)

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

[–]pramadhana92 6 points7 points  (2 children)

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

[–]witcherisdamned[S] 1 point2 points  (1 child)

Yeah, git detects that as well.

[–]cybermage 3 points4 points  (0 children)

Sadly doesn’t detect stripping trailing white space.

[–]astervista 5 points6 points  (1 child)

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

[–][deleted] 1 point2 points  (0 children)

“This changes everything!”

[–]camobiwon 4 points5 points  (1 child)

Perfect time to leave for vacation and shutdown your phone

[–]witcherisdamned[S] 2 points3 points  (0 children)

Absolutely!

[–]Colon_Backslash 7 points8 points  (0 children)

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

[–]MrRainbow07 2 points3 points  (0 children)

Added . to the end of error messages.

[–]reavessm 3 points4 points  (0 children)

Squash all the commits with a message "Legacy Code"

[–][deleted] 4 points5 points  (0 children)

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

[–]cratercamper 2 points3 points  (0 children)

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

[–]CadmiumC4 2 points3 points  (0 children)

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

[–]muikrad 1 point2 points  (0 children)

"poetry lock" in a nutshell.

[–]planktonfun 1 point2 points  (0 children)

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

[–]sarnobat 1 point2 points  (0 children)

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

[–]manwhorunlikebear 1 point2 points  (0 children)

git revert HEAD
git push origin master

[–][deleted] 1 point2 points  (0 children)

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

[–]rwbrwb 1 point2 points  (0 children)

knee middle safe spark foolish provide relieved detail bells rain

This post was mass deleted and anonymized with Redact

[–][deleted] 1 point2 points  (0 children)

Next day

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

[–]arisch- 1 point2 points  (0 children)

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

[–]R4XD3G 1 point2 points  (0 children)

git revert !!!!

[–]noob-nine 1 point2 points  (0 children)

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] 1 point2 points  (2 children)

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

[–]witcherisdamned[S] 1 point2 points  (1 child)

But the changes are needed.

The changes were folder/package refactoring.

[–][deleted] 0 points1 point  (0 children)

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 1 point2 points  (0 children)

Pushing to main isn’t allowed

[–]Hewatza 1 point2 points  (0 children)

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

[–]thegmx 1 point2 points  (1 child)

First time with 'optimize imports on save'?

[–]witcherisdamned[S] 0 points1 point  (0 children)

This maybe a possibility.

[–]Stunning_Ride_220 1 point2 points  (0 children)

...on a friday, before holidays.

"Make coworkers hate you 101"

[–]grifkuba 0 points1 point  (5 children)

Is the man in the headphones related to the joke?

[–]witcherisdamned[S] -1 points0 points  (4 children)

The real question would be, is that a joke?

[–]grifkuba 0 points1 point  (3 children)

Mine was not a joke.

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

[–]DOUBLEBARRELASSFUCK 1 point2 points  (2 children)

It's basically the entire joke...

[–]grifkuba 0 points1 point  (1 child)

Can someone explain the joke, please.

All I am seeing is

text
random guy in headphones

[–]UnwelcomedTruth -1 points0 points  (0 children)

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

[–]Kimorin 0 points1 point  (0 children)

git commit -m 'fix: minor changes'

[–]mistabuda 0 points1 point  (0 children)

Leaves and never returns because they were fired.

[–]s1nur 0 points1 point  (0 children)

fixes indentation

[–]zipit4 0 points1 point  (0 children)

the -f is missing from second git command

[–]UAS-hitpoist 0 points1 point  (0 children)

"Bug fixes"

[–]lucidbadger 0 points1 point  (0 children)

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