soggy_kitty,

Sorry to be that guy but I don’t think it’s smart to put this anywhere in public, keep this shit somewhere private as a joke

barsoap,

This is a lawsuit waiting to happen. Anyway any of you ever heard of ACID? Why aren’t our undo buffers durable and integrated with version control? Squash and forget the individual keystrokes as soon as an actual commit is made.

HiddenLayer5,
@HiddenLayer5@lemmy.ml avatar

Counterpoint: Virtualized environment/remote desktop. The real computer is in a data center hundreds of kilometers away with world class fire suppression systems.

Counter counterpoint: If you’re virtualized you might be working from home, in which case, that’s rough, hope they manage to restore your house.

RollForInitiative,

With a laggy desktop experience i also can’t really configure how i want? No thank you. It’s bad enough i have to use Windows for software development instead of letting me install Linux

HiddenLayer5,
@HiddenLayer5@lemmy.ml avatar

I like it because I don’t have any of the company’s shit on my own machine. I absolutely don’t trust them not to spy on my personal computer use if they had access to it. With remote desktop I close it at the end of the work say and it has no more access to my computer than I have access to their critical systems.

In my case, their shit that we’re required to use don’t even support Linux so if it wasn’t for virtualized environment I’d had to install Windows on my own machine.

RollForInitiative,

Fair, good point. I guess i’m lucky that i don’t have to use my own devices, my machine is provided by my employer.

Immersive_Matthew,

Another reason I just manually backup my project and avoid Git despite all my other developer friends shaming me. One command and I am out of there.

meliaesc,

That doesn’t hold up so well when you work with other people on a project.

Immersive_Matthew,

Yes and no depending on what you are working on.

meliaesc,

Merging conflicts will be an issue no matter what you’re working on. Maintaining different sets of code bases based on the version/release will be an issue even when working alone.

Immersive_Matthew,

Can you describe a situation that underscores this issue as I am not seeing it, but maybe I experience it and do not even realize.

meliaesc, (edited )

Situation: You’re building some software to display emojis based on user input.

Current code: when user types “happy”, output 🙂

  • Your new requirement: when user types “happy”, output 😃 instead of 🙂
  • Coworker’s new requirement: when user types “sad”, output 😭

You implement your change, back it up, and the new version with 😀 is released. But it turns out 😃 is the ultimate insult in the Snowflake region, and you need to immediately rollback 😃 back to 🙂 while you find an alternative.

Meanwhile, Coworker has added 😭 to your backup, which still has 😃. Now when you try to rollback to 🙂, Coworker’s code gets erased. Now your code is unable to safely support both 😭 with 🙂 without starting over entirely. Maybe you want to disable 😀 only for the Snowflake region, but that’s not possible either without harding coding the regions instead of just changing the deployment.

Now imagine working with a team of 10 people, or a company with 100 people working on this same software. With features and release dates constantly changing.

Immersive_Matthew,

I would agree with more people these tools become more needed, but I am talking about a solo dev situation who is the only person who accesses the code base. All other contributors I carefully import.

quackers,

That doesnt sound like a good reason. What other reasons could you possibly have to do copypasta backups over what you can at least use as a diff based backup letting you still access any old version you want

Immersive_Matthew,

I just find frequent full backups give me more control and less surprises when I find out my code did not sync/commit or some other issue. Done it for 3 years and it has been very worthwhile. Saved my project from a loss so many times now.

mercano,
@mercano@lemmy.world avatar

First, git checkout -b omgFire, then do the rest.

xantoxis,

And if your git repo is self-hosted on-prem, you’d better be helping pack it and carry it out.

lukas,
@lukas@lemmy.haigner.me avatar

What about git add?

osmn,

“I followed the rules, Boss. Not my fault the rules are stupid 🤷‍♂️”

applebusch,

You could change it to git commit . to add and commit everything. But just in case you weren’t up to date, you should probably do


<span style="color:#323232;">git commit .
</span><span style="color:#323232;">
</span><span style="color:#323232;">git pull -s ours
</span><span style="color:#323232;">
</span><span style="color:#323232;">git push
</span>

For maximum chaos.

CaptainBlagbird,
@CaptainBlagbird@lemmy.world avatar

git fire

MoonRaven,
@MoonRaven@feddit.nl avatar

*git out

dirtbiker509,

*git -tf out

hakunawazo,

If the flames are nearby I would be so reckless and execute git push --force.
I don’t want to die for a merge conflict.
But maybe then the team will burn me later.

spongeborgcubepants,

Just push to a new branch

dirtySourdough,

I’ve got something similar on my office door that reads

In case of fire<br> git commit -a<br> git push<br> git -tf out

Piemanding,

Mark this shit NSFW. I could have viewed it at work.

kd45,

Cause of death: 15 minute long pre-push hook

redeven,
@redeven@lemmy.world avatar

Just

git add . &amp;&amp; git commit -m “sorry theres a fire” &amp;&amp; git push -u origin feature/fire

And run out. It will eventually finish pushing. Or not.

PoolloverNathan,

git add .; git commit -nm fire --no-gpgsign; git push -n origin fire/${USER}

PrettyFlyForAFatGuy,

i read a reddit post years ago where a someone wrote a script that iterates through all the projects in their dev folder, for each project creating a new branch, committing and pushing.

they then aliased it to “fire” or “panic” or something like that.

not a bad idea really

flashgnash,

As in one they’d manually run if there was a fire?

icedterminal,

Exactly. The alias just points to the script which is executed.

flashgnash,

Ohh I see so you just run git fire?

PrettyFlyForAFatGuy,

if its aliased you should be able to just run “fire” and it does the rest

flashgnash,

Oh bash alias right

18107,

git-fire

nao,

no changes added to commit (use “git add” and/or “git commit -a”)

rufus, (edited )

It should (at least) be:


<span style="color:#323232;">git commit -a -m "🚨🔥🚨"
</span><span style="color:#323232;">git push --force
</span>

Better, create a new branch and push it to origin(?).

Relevant The IT Crowd

IAm_A_Complete_Idiot,

Better have not created any new files tho - git commit -a doesn’t catch those without an add first.

ZephyrXero,

So we need git add . && git commit -a here really

IAm_A_Complete_Idiot,

In which case the -a isn’t needed.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • random
  • uselessserver093
  • Food
  • aaaaaaacccccccce
  • [email protected]
  • test
  • CafeMeta
  • testmag
  • MUD
  • RhythmGameZone
  • RSS
  • dabs
  • Socialism
  • KbinCafe
  • TheResearchGuardian
  • oklahoma
  • feritale
  • SuperSentai
  • KamenRider
  • All magazines
    •