chore: disable welcome bot
Piotr Galar committed
Oct 29, 2022 at 12:37 UTC
518fc32511774e23c05ff9b1748ebb3e573462ab
1 file changed
-68
.github/config.yml
deleted
-68
@@ -1,68 +0,0 @@
1
-# Configuration for welcome - https://github.com/behaviorbot/welcome
2
-
3
-# Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
4
-# Comment to be posted to on first time issues
5
-newIssueWelcomeComment: >
6
- Thank you for submitting your first issue to this repository! A maintainer
7
- will be here shortly to triage and review.
8
-
9
- In the meantime, please double-check that you have provided all the
10
- necessary information to make this process easy! Any information that can
11
- help save additional round trips is useful! We currently aim to give
12
- initial feedback within **two business days**. If this does not happen, feel
13
- free to leave a comment.
14
-
15
- Please keep an eye on how this issue will be labeled, as labels give an
16
- overview of priorities, assignments and additional actions requested by the
17
- maintainers:
18
-
19
- - "Priority" labels will show how urgent this is for the team.
20
- - "Status" labels will show if this is ready to be worked on, blocked, or in progress.
21
- - "Need" labels will indicate if additional input or analysis is required.
22
-
23
- Finally, remember to use https://discuss.ipfs.io if you just need general
24
- support.
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
-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
67
-# Currently disabled
68
-#firstPRMergeComment: ""