PR autocomment: Only comment for first-time contributors
Hector Sanjuan committed
May 4, 2020 at 10:55 UTC
9c7cdac16c4d97a6ccb0de18032f0d69ac5a4e60
2 files changed
+38
-38
.github/auto-comment.yml
+2
-36
@@ -2,39 +2,5 @@
2
# Disabled
3
# issueOpened: ""
4
5
-pullRequestOpened: >
6
-
7
- Thank you for submitting this PR!
8
-
9
- A maintainer will be here shortly to review it.
10
-
11
- We are super grateful, but we are also overloaded! Help us by making sure
12
- that:
13
-
14
- * The context for this PR is clear, with relevant discussion, decisions
15
- and stakeholders linked/mentioned.
16
-
17
- * Your contribution itself is clear (code comments, self-review for the
18
- rest) and in its best form. Follow the [code contribution
19
- guidelines](https://github.com/ipfs/community/blob/master/CONTRIBUTING.md#code-contribution-guidelines)
20
- if they apply.
21
-
22
- Getting other community members to do a review would be great help too on
23
- complex PRs (you can ask in the chats/forums). If you are unsure about
24
- something, just leave us a comment.
25
-
26
- Next steps:
27
-
28
- * A maintainer will triage and assign priority to this PR, commenting on
29
- any missing things and potentially assigning a reviewer for high
30
- priority items.
31
-
32
- * The PR gets reviews, discussed and approvals as needed.
33
-
34
- * The PR is merged by maintainers when it has been approved and comments addressed.
35
-
36
- We currently aim to provide initial feedback/triaging within **two business
37
- days**. Please keep an eye on any labelling actions, as these will indicate
38
- priorities and status of your contribution.
39
-
40
- We are very grateful for your contribution!
5
+# Disabled
6
+# pullRequestOpened: ""
.github/config.yml
+36
-2
@@ -25,8 +25,42 @@ newIssueWelcomeComment: >
25
26
# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
27
# Comment to be posted to on PRs from first time contributors in your repository
28
-# Currently disabled
29
-# newPRWelcomeComment: ""
28
+newPRWelcomeComment: >
29
+ Thank you for submitting this PR!
30
+
31
+ A maintainer will be here shortly to review it.
32
+
33
+ We are super grateful, but we are also overloaded! Help us by making sure
34
+ that:
35
+
36
+ * The context for this PR is clear, with relevant discussion, decisions
37
+ and stakeholders linked/mentioned.
38
+
39
+ * Your contribution itself is clear (code comments, self-review for the
40
+ rest) and in its best form. Follow the [code contribution
41
+ guidelines](https://github.com/ipfs/community/blob/master/CONTRIBUTING.md#code-contribution-guidelines)
42
+ if they apply.
43
+
44
+ Getting other community members to do a review would be great help too on
45
+ complex PRs (you can ask in the chats/forums). If you are unsure about
46
+ something, just leave us a comment.
47
+
48
+ Next steps:
49
+
50
+ * A maintainer will triage and assign priority to this PR, commenting on
51
+ any missing things and potentially assigning a reviewer for high
52
+ priority items.
53
+
54
+ * The PR gets reviews, discussed and approvals as needed.
55
+
56
+ * The PR is merged by maintainers when it has been approved and comments addressed.
57
+
58
+ We currently aim to provide initial feedback/triaging within **two business
59
+ days**. Please keep an eye on any labelling actions, as these will indicate
60
+ priorities and status of your contribution.
61
+
62
+ We are very grateful for your contribution!
63
+
64
65
# Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
66
# Comment to be posted to on pull requests merged by a first time user