Add CI workflow to check authors name against release tools #3599
Conversation
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
jessica-mitchell
added
S: Normal
jessica-mitchell
added
the
I: No breaking change
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR adds a workflow in nestbuildmatrix/buld_support that, for every PR, checks the author(s) who contributed on that PR. It then compares these authors to those in our nest-release repo to see if they are included in our 'validated authors' list. This includes authors who have contributed but whose author names or email addresses have changed.
This CI job will flag any author who is not found so we can add them to the release workflow, ensure we have their CA and other info.
The reasoning for this is to minimize the amount of work needed to be done at release time;
If we have all the author information at time of PR we can save time during the release process.
The CI job is currently set up so that even if access to the private nest-releases repo is not authorized; the names of the authors of the current pr will be logged.