We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We are experiencing strange behavior when we force push branches in a PR.
We see that there will be "no new release" generated, even when it's pretty clear that there is a commit with a change that would generate the change.
When I first committed the changes, it generated release notes. Then when I rebased and force pushed changes up, it did not.
Here is the commit message:
Here's the output:
And we are setting the fetch depth to 0
0
steps: - uses: actions/checkout@v3 with: fetch-depth: 0 - run: npm install - name: Generate release notes id: release-notes-preview uses: guilhermetod/[email protected]
The text was updated successfully, but these errors were encountered:
semantic-release
No branches or pull requests
We are experiencing strange behavior when we force push branches in a PR.
We see that there will be "no new release" generated, even when it's pretty clear that there is a commit with a change that would generate the change.
When I first committed the changes, it generated release notes. Then when I rebased and force pushed changes up, it did not.
Here is the commit message:
Here's the output:
And we are setting the fetch depth to
0
The text was updated successfully, but these errors were encountered: