Repository navigation
Conversation
This branch has not been deployed
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
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.
A merged PR counts on the leaderboard only when it has
hacktoberfest-accepted. Today codercops/chatcops#165 and codercops/chatcops#166 were merged without it, so they didn't count until the label was added by hand.This workflow runs when a PR is merged and adds the label when:
spamOtherwise it leaves a notice on the run and changes nothing. It only runs at the merge, so removing the label afterwards sticks.
It uses
pull_request_targetso it can label fork PRs, withpull-requests: writeandissues: read. It never checks out or runs the PR's code.How I tested this
I ran the script against merged PRs with the label call replaced by a print. codercops/chatcops#165, #166 and #167, #139 and #181, and codercops/discord-bot#29 would get the label. codercops/ogcops#103 wouldn't, since its issue wasn't assigned to its author, and a PR without a linked issue only gets the notice.