legal: require signing of CLA by external contributors #1190
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
|
This makes sense! Want to get back to it over the next days. |
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.
Opening a proposal that external contributors are required to sign a CLA (contents undefined) which is enforced via GitHub Actions.
Next steps:
CLA_GITHUB_TOKENtoken which has write access tonamespacelabs/claSee https://github.com/coder/cla/tree/main as an example of this running in the wild
Each time
https://github.com/namespacelabs/cla/README.mdis updated then the workflow should bump the vYYYY-MM-DD` field in the GitHub Actions yaml to ensure folks read/review/sign with the updated terms.