Actually perform the push and revert

[tsjost]

We want to actually signal the remote that we're doing something, and then suspend our changes.

[VChoubard]

Nice!! At least now it is actually doing something!

[alanbover]

can you add a shebang line?

[tsjost]

fix'd

[alanbover]

for i in {1..8}

[tsjost]

fix'd

[alanbover]

check if git exists

[tsjost]

@alanbover Feel free to perform those changes in a separate pull request ;)

[alanbover]

@tsjost your standards are not approved by european union, so the whole process is invalid, and I have 155 reasons to provide you

[VChoubard]

Please merge this! @voghDev

[calas]

Not a good idea, actually reverting a pushed commits would mean rewriting history... well... it should be implemented. Maybe in the ANC branch?

[tsjost]

It's not really rewriting history per se; just restoring the state of the remote like it was before pushing, while still allowing all the 155 different git hooks to execute.

[voghDev]

Hi everyone,

thanks for the support and the contributions @tsjost @jhg-tgu @VChoubard @alanbover

performing the real execution of the command then reverting the results by rewriting the history can be risky, and someone may suffer data loss or any inconsistence when "performing a demo" of the command in his or her repository. It would be really bad if this happens, and it would be in part my fault. The command was thought to laugh, have some fun and of course not to damage anyone's code :-P

Also, printing just words (echo's) and not performing any real action is funnier and maybe closer to the reality :))

That's why I think it is better to keep the command just as pure fun, and not causing a real effect on people's repositories. Feel free to express your opinions about this.

Again, thanks everyone and I hope you liked and enjoyed the command

Peace!

[tsjost]

@voghDev As I said above, the script will restore the remote repo to the state it was in before the script was executed (however I haven't verified that it will work in all cases e.g. in a merge conflict state or such weird things).

But alas, I will have to maintain my own fork then :)