ci: configure gh action for F5 CLA tooling pilot #365
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
|
Hey @TasoOneAsia, thanks for this! Can you also add @lee00678 to the list of maintainers? |
|
@reb-dev All set, I added him to the whitelist |
reb-dev
approved these changes
Apr 11, 2024
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.
Proposed Changes
Adds a GitHub action file configured for the F5 CLA tooling pilot. This action is configured to target a shared signature store for all F5 open-source projects participating in this pilot. As part of the configuration, the following GitHub usernames were whitelisted as maintainers:
reb-devlee00678Any contributors who submit a pull request and have not yet signed an F5 CLA through the new tooling will be prompted to view and agree to the terms of F5's CLA through a pull request comment.
As part of this PR, any F5 CLAs previously sent to
[email protected]have also been migrated to the new tooling; these users should not be prompted when opening pull requests.Please let me know if there are any other questions :)