Add Github release configuration #162
Merged
Conversation
This file contains 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
|
When you create a new release on Github you can have it automatically generate a change log for you, based on the PRs since the last tag. See https://github.com/Ericsson/puppet-module-vas/releases/tag/v1.1.0 for example. This would let us add a label to PRs that we want excluded from the release notes like the release commit itself (#158 in this case) |
|
If we want to enable branch protection, all changes would need to come from PRs. So this is simply to prevent such PRs from being added to Release notes automatically. |
|
Well, that sounds not too bad. We should give it a try. |
anders-larsson
force-pushed
the
release_config
branch
from
bbf8aa5 to
f111e5c
Compare
|
Changed label to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add Github release configuration to automatically exclude PRs with tag
exclude-changelog. This tag would also need to be excluded when runninggithub_changelog_generatorto generate CHANGELOG.md.Should we use this tag och change it to something else? Github's documentation uses
ignore-for-release. Maybe that is better.