On Thursday, 31 August 2023 at 18:49:35 UTC+10 mag...@therning.org wrote:
What you are trying to do is to rewrite history on the central git repo. While git allows doing that, it does require you to signal that you are completely sure you know what you are doing. Look at '--force' and related flags in 'git push --help'. If you are working on this repo by yourself you can pretty much do whatever you want, but if you work with others and they have based any of their work on the 'staging' branch after you merged in your 'feature-branch', then you should look at 'git revert --help' instead. Ok. This makes sense - I am working alone so I can force - if I was in a team, this would cause problems. So effectively, git has no easy "undo" option and requires manual removal of code There are at least a coupld of things you can do - invest in ways to test locally, then you don't have to push at all. - invest in ways to test on your 'feature-branch', then you don't have to merge into 'staging' (and push the merge) Testing changes has zero affect on business decisions deciding that changes previously requested are no longer viable. It is impossible to test a code base against the management teams inner thoughts and market forces! -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/85cff136-7745-464e-8113-c9f0ab52a8dbn%40googlegroups.com.
