Skip to content
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

Add preartefact-changelog-check.bash command #42

Merged
merged 1 commit into from
May 4, 2021
Merged

Add preartefact-changelog-check.bash command #42

merged 1 commit into from
May 4, 2021

Conversation

SeanTAllen
Copy link
Member

The preartefact-changelog-check.bash command validates that the changelog
contains an entry for X.Y.Z where X.Y.Z is the release that is underway.

The command can be used to protect against misconfiguration of workflows and
more importantly, a user inadvertently pushing a X.Y.Z tag to start a release
rather than the correct release-X.Y.Z.

Closes #26

@SeanTAllen SeanTAllen added the changelog - added Automatically add "Added" CHANGELOG entry on merge label May 4, 2021
@SeanTAllen SeanTAllen force-pushed the 26 branch 4 times, most recently from feca493 to 3787be7 Compare May 4, 2021 18:46
The preartefact-changelog-check.bash command validates that the changelog
contains an entry for `X.Y.Z` where `X.Y.Z` is the release that is underway.

The command can be used to protect against misconfiguration of workflows and
more importantly, a user inadvertently pushing a `X.Y.Z` tag to start a release
rather than the correct `release-X.Y.Z`.

Closes #26
@SeanTAllen SeanTAllen merged commit e86180f into main May 4, 2021
@SeanTAllen SeanTAllen deleted the 26 branch May 4, 2021 18:48
github-actions bot pushed a commit that referenced this pull request May 4, 2021
github-actions bot pushed a commit that referenced this pull request May 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog - added Automatically add "Added" CHANGELOG entry on merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Verify during release step that "start" step has been done
1 participant