Allow Editing Release-Please PR without Force Push #1058
Labels
priority: p3
Desirable enhancement or fix. May not be included in next release.
type: question
Request for information or clarification. Not an issue.
Hi there,
We use release-please PRs to aggregate our CHANGELOG, but also as the branch that we deploy staging from. We have some Github Actions that only run on the release-please branch and it will update some of the files in the branch accordingly and run some tests. We've noticed this problem where these files that get updated will get reverted during a "force-push" when a new PR is merged with main. Instead of preserving these changes, the force-push reverts the state of the PR to the latest set of changes made to the CHNAGELOG and corresponding plugin files. Is there a way to configure this force-push behavior and instead configure a merge strategy so we can keep the changes that were already triggered by our actions?
Here is how we trigger release-please:
Here's our release-please-config.json
The text was updated successfully, but these errors were encountered: