config.yml 2.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768
  1. # Configuration for welcome - https://github.com/behaviorbot/welcome
  2. # Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
  3. # Comment to be posted to on first time issues
  4. newIssueWelcomeComment: >
  5. Thank you for submitting your first issue to this repository! A maintainer
  6. will be here shortly to triage and review.
  7. In the meantime, please double-check that you have provided all the
  8. necessary information to make this process easy! Any information that can
  9. help save additional round trips is useful! We currently aim to give
  10. initial feedback within **two business days**. If this does not happen, feel
  11. free to leave a comment.
  12. Please keep an eye on how this issue will be labeled, as labels give an
  13. overview of priorities, assignments and additional actions requested by the
  14. maintainers:
  15. - "Priority" labels will show how urgent this is for the team.
  16. - "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  17. - "Need" labels will indicate if additional input or analysis is required.
  18. Finally, remember to use https://discuss.ipfs.io if you just need general
  19. support.
  20. # Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
  21. # Comment to be posted to on PRs from first time contributors in your repository
  22. newPRWelcomeComment: >
  23. Thank you for submitting this PR!
  24. A maintainer will be here shortly to review it.
  25. We are super grateful, but we are also overloaded! Help us by making sure
  26. that:
  27. * The context for this PR is clear, with relevant discussion, decisions
  28. and stakeholders linked/mentioned.
  29. * Your contribution itself is clear (code comments, self-review for the
  30. rest) and in its best form. Follow the [code contribution
  31. guidelines](https://github.com/ipfs/community/blob/master/CONTRIBUTING.md#code-contribution-guidelines)
  32. if they apply.
  33. Getting other community members to do a review would be great help too on
  34. complex PRs (you can ask in the chats/forums). If you are unsure about
  35. something, just leave us a comment.
  36. Next steps:
  37. * A maintainer will triage and assign priority to this PR, commenting on
  38. any missing things and potentially assigning a reviewer for high
  39. priority items.
  40. * The PR gets reviews, discussed and approvals as needed.
  41. * The PR is merged by maintainers when it has been approved and comments addressed.
  42. We currently aim to provide initial feedback/triaging within **two business
  43. days**. Please keep an eye on any labelling actions, as these will indicate
  44. priorities and status of your contribution.
  45. We are very grateful for your contribution!
  46. # Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
  47. # Comment to be posted to on pull requests merged by a first time user
  48. # Currently disabled
  49. #firstPRMergeComment: ""