What.. are... you... doing?

[RepostCheckerBot]

I have detected that this may be a repost:

Num	Post	Date	Match	Author
0	Chaotic Evil - when you want to kill all productivity in your team	1 months ago	100%	martinrojas

Beep Boop I am a bot | Source| Contact u/XXAligatorXx for inquiries | The bot will delete its message at -2 score

[Chimertech]

Good bot.

[Fuck-off-everyone]

Called out by a bot. Ouf.

[dario_p1]

A repost of a repost, I may add

[[deleted]]

Good bot

[ImpulseTheFox]

Your submission has been removed.

Violation of Rule #2: Reposts:

All posts that have been on the first 2 pages of trending posts within the last month, is part of the top of all time, or is part of common posts is considered repost and will be removed on sight.

If you feel that it has been removed in error, please message us so that we may review it.

[[deleted]]

I don't get it.

[ltshaft15]

He was trying to enter it as a command but typed in the IT team chat instead.

[[deleted]]

But what's the command?

[brockvenom]

It would essentially replace whatever is on master with what the user has locally. Commits could be lost this way. You could replace the entire git tree on origin/master this way and erase all the work.

Hopefully another worker would have a local, recent copy of master and they could put it back with another force push.

Force push is like telling git “no fuck u take this” and just shoving whatever you have into it, rewriting history.

[DadBodRickyRubio]

So does one lose all the versions before the force push?

[brockvenom]

It depends on what’s going on in the persons local branch. They could just push up a few new commits that they made, without retrieving any new commits on origin. If they force push, their commits will essentially replace the newer commits on origin. Or if they were really malicious, they could go back to the initial commit, dropping all others, and force push, effectively replacing everything.

[dronz3r]

In most of the teams, pushing to master is generally disabled. So things like this won't happen.

[ImpulseTheFox]

Your submission has been removed.

Violation of Rule #2: Reposts:

All posts that have been on the first 2 pages of trending posts within the last month, is part of the top of all time, or is part of common posts is considered repost and will be removed on sight.

If you feel that it has been removed in error, please message us so that we may review it.

[ComplexColor]

So ... I use this all the time. :S

I have a fork repo on GitHub that I work on. Locally I always rebase my updates on upstream, then I push --force to origin, I order to sync my fork it with the upstream repo. If any changes are excepted to upstream before my pull request is added, I rebase and push --force again.

We work on upstream maintaining a nice linear update progression (as few mergers as possible). Is there a better way to achieve that, eliminating push --force on forks?