New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Previous git notes are being overwritten rather than merged #3097
Comments
by using a squash merge, you are rewriting history in a way that is losing the details you are describing. dont squash your release branches. |
@travi we only squash the PR's into staging (default branch). PR's into main and LTS are not squashed. |
It happens to us as well when we fast-forward merge a higher branch (e.g. In const higherChannels = branches
// Consider only releases of higher branches
.slice(branches.findIndex(({ name }) => name === branch.name) + 1)
// Exclude prerelease branches
.filter(({ type }) => type !== "prerelease")
.map(({ channel }) => channel || null); Is it intentional to work like this? Update: |
Current behavior
Given the following branching strategy.
staging (default branch, channel: beta) -> main (channel: RC) -> LTS
Expected behavior
Subsequent commits into staging do not cause a duplicate tag error.
semantic-release
version21.1.1
CI environment
Github Actions
Plugins used
These are documented in in the config below.
semantic-release
configurationCI logs
Show notes before action
Show notes after action
The text was updated successfully, but these errors were encountered: