mirror of
https://github.com/ipfs/kubo.git
synced 2025-05-17 15:06:47 +08:00
PR autocomment: Only comment for first-time contributors
This commit is contained in:
38
.github/auto-comment.yml
vendored
38
.github/auto-comment.yml
vendored
@ -2,39 +2,5 @@
|
||||
# Disabled
|
||||
# issueOpened: ""
|
||||
|
||||
pullRequestOpened: >
|
||||
|
||||
Thank you for submitting this PR!
|
||||
|
||||
A maintainer will be here shortly to review it.
|
||||
|
||||
We are super grateful, but we are also overloaded! Help us by making sure
|
||||
that:
|
||||
|
||||
* The context for this PR is clear, with relevant discussion, decisions
|
||||
and stakeholders linked/mentioned.
|
||||
|
||||
* Your contribution itself is clear (code comments, self-review for the
|
||||
rest) and in its best form. Follow the [code contribution
|
||||
guidelines](https://github.com/ipfs/community/blob/master/CONTRIBUTING.md#code-contribution-guidelines)
|
||||
if they apply.
|
||||
|
||||
Getting other community members to do a review would be great help too on
|
||||
complex PRs (you can ask in the chats/forums). If you are unsure about
|
||||
something, just leave us a comment.
|
||||
|
||||
Next steps:
|
||||
|
||||
* A maintainer will triage and assign priority to this PR, commenting on
|
||||
any missing things and potentially assigning a reviewer for high
|
||||
priority items.
|
||||
|
||||
* The PR gets reviews, discussed and approvals as needed.
|
||||
|
||||
* The PR is merged by maintainers when it has been approved and comments addressed.
|
||||
|
||||
We currently aim to provide initial feedback/triaging within **two business
|
||||
days**. Please keep an eye on any labelling actions, as these will indicate
|
||||
priorities and status of your contribution.
|
||||
|
||||
We are very grateful for your contribution!
|
||||
# Disabled
|
||||
# pullRequestOpened: ""
|
||||
|
38
.github/config.yml
vendored
38
.github/config.yml
vendored
@ -25,8 +25,42 @@ newIssueWelcomeComment: >
|
||||
|
||||
# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
|
||||
# Comment to be posted to on PRs from first time contributors in your repository
|
||||
# Currently disabled
|
||||
# newPRWelcomeComment: ""
|
||||
newPRWelcomeComment: >
|
||||
Thank you for submitting this PR!
|
||||
|
||||
A maintainer will be here shortly to review it.
|
||||
|
||||
We are super grateful, but we are also overloaded! Help us by making sure
|
||||
that:
|
||||
|
||||
* The context for this PR is clear, with relevant discussion, decisions
|
||||
and stakeholders linked/mentioned.
|
||||
|
||||
* Your contribution itself is clear (code comments, self-review for the
|
||||
rest) and in its best form. Follow the [code contribution
|
||||
guidelines](https://github.com/ipfs/community/blob/master/CONTRIBUTING.md#code-contribution-guidelines)
|
||||
if they apply.
|
||||
|
||||
Getting other community members to do a review would be great help too on
|
||||
complex PRs (you can ask in the chats/forums). If you are unsure about
|
||||
something, just leave us a comment.
|
||||
|
||||
Next steps:
|
||||
|
||||
* A maintainer will triage and assign priority to this PR, commenting on
|
||||
any missing things and potentially assigning a reviewer for high
|
||||
priority items.
|
||||
|
||||
* The PR gets reviews, discussed and approvals as needed.
|
||||
|
||||
* The PR is merged by maintainers when it has been approved and comments addressed.
|
||||
|
||||
We currently aim to provide initial feedback/triaging within **two business
|
||||
days**. Please keep an eye on any labelling actions, as these will indicate
|
||||
priorities and status of your contribution.
|
||||
|
||||
We are very grateful for your contribution!
|
||||
|
||||
|
||||
# Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
|
||||
# Comment to be posted to on pull requests merged by a first time user
|
||||
|
Reference in New Issue
Block a user