chore: introduce github merit badger workflow#21898
Merged
mergify[bot] merged 8 commits intomainfrom Sep 21, 2022
Merged
Conversation
|
|
corymhall
approved these changes
Sep 21, 2022
| permissions: | ||
| pull-requests: write | ||
| steps: | ||
| - uses: kaizencc/github-merit-badger@main |
Contributor
There was a problem hiding this comment.
@kaizencc Should we move this somewhere in cdklabs?
Contributor
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Collaborator
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Contributor
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
mergify bot
pushed a commit
that referenced
this pull request
Sep 22, 2022
This PR piggybacks on #21898.
homakk
pushed a commit
to homakk/aws-cdk
that referenced
this pull request
Dec 1, 2022
See [merit badger readme](https://github.com/kaizencc/github-merit-badger#readme) for an overview of the github action that is introduced in this PR. The idea is that a "merit badge" will be applied to every incoming PR via label based on prior (successfully merged) contributions to the CDK. The badges are as follows: - `beginning-contributor`: contributed between 0-2 PRs to the CDK - `repeat-contributor`: contributed between 3-5 PRs to the CDK - `valued-contributor`: contributed between 6-12 PRs to the CDK - `admired-contributor`: contributed between 13-24 PRs to the CDK - `star-contributor`: contributed between 25-49 PRs to the CDK - `distinguished-contributor`: contributed 50+ PRs to the CDK We will **not** label PRs that come from the core team. Special thanks to @scanlonp and @Tianyi-W if/when this does get merged.
homakk
pushed a commit
to homakk/aws-cdk
that referenced
this pull request
Dec 1, 2022
This PR piggybacks on aws#21898.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
See merit badger readme for an overview of the github action that is introduced in this PR.
The idea is that a "merit badge" will be applied to every incoming PR via label based on prior (successfully merged) contributions to the CDK. The badges are as follows:
beginning-contributor: contributed between 0-2 PRs to the CDKrepeat-contributor: contributed between 3-5 PRs to the CDKvalued-contributor: contributed between 6-12 PRs to the CDKadmired-contributor: contributed between 13-24 PRs to the CDKstar-contributor: contributed between 25-49 PRs to the CDKdistinguished-contributor: contributed 50+ PRs to the CDKWe will not label PRs that come from the core team.
Special thanks to @scanlonp and @Tianyi-W if/when this does get merged.