Add pr-feedback.yml#674
Conversation
Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>
PHP Code CoverageCoverage after merging ci/noid/prFeedback into master will be
Coverage Report
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
@AndyScherzinger note that PR feedback is being posted on various PRs that are already merged and closed. Example: #638 (comment) |
|
@phil-davis exactly, yes. It has a date configured as a starting point in the past as a max where it shall ask for feedback and any future PR. So yes. It is a one time effect 👍 |
|
So as the bot states in the comment it posts, you can also add yourself to the blocklist at https://github.com/nextcloud/.github/blob/master/non-community-usernames.txt so it ignores your PRs when asking for feedback. This is particularly helpful for folks pushing several, regularly PRs since it might get annoying. However we introduced it to add another feedback channel for community to get things reported that make peoples live hard in terms of contributing. |
Description
Harmonizing the repositories in the nextcloud Github organization adding a feedback bot to the repos still lacking it
Related Issue or Workpackage
Screenshots (if appropriate):
Types of changes
Checklist:
CHANGELOG.mdfile