Conversation
pepicrft
commented
Jan 22, 2025
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
| with: | ||
| commitTitleMatch: "false" | ||
| ignoreCommits: true |
Contributor
Author
There was a problem hiding this comment.
I changed the configuration of the squash & merge commit to match the title of the PR, so this is no longer necessary:
fortmarek
approved these changes
Jan 22, 2025
cschmatzler
approved these changes
Jan 22, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I noticed our release notes contain an
[Unrelease]section. It turns out there's a bug in our release automation that causes that section to be present. This PR fixes it by first updating the CHANGELOG, and then usinggit cliffto get the latest version.