Repository navigation
Disable force push #455
Description
Activity
Another reason to do this is that it would be really nice to retain the commits in a release branch over time. If a release PR is open for a while and needs additional work to get it mergeable/publishable, I want the ability to understand the history of that PR. Force push makes this impossible.
I've looked into this but it's not very feasible to implement it. For example:
- If main adds a changeset, you need to merge first to sync so you can delete the changeset on version
- If main updates a changeset, you need to reset first (to prevent conflicts), merge to sync, and then you can delete the changeset on version.
So this would always be generating at least 2-3 commits per update. While we can also try to collapse the commits, the merge commit makes this tricky and it's not really a good practice to mix unrelated changes inside a merge commit. Furthermore, it also mixes up the merge changes so it doesn't help with checking the git history either.
As discussed on discord, we decided to not support this for now.
Currently this action is using force push
/usr/bin/git push origin HEAD:changeset-release/qa --forceto push package.json and release changes but my organisation doesn't allow force push.Is there any way to disable this force push?