You've already forked library-registry
mirror of
https://github.com/arduino/library-registry.git
synced 2025-07-09 01:42:00 +03:00
More clearly communicate that new PR is not required to resolve submission problem
The system is designed to allow a submission to be accomplished in a single pull request. This is the case even when initial passes of checks reveal problems that block acceptance. The checks will automatically re-run any time the PR author pushes to the PR's branch or mentions the bot. Although the submitters are welcome to submit a new PR if that is their preference, it is a less efficient approach, both for them and the maintainer. So it's important to clearly communicate that the submission process can be continued via the current PR if that is convenient to them. Usage patterns indicate that this is not clearly communicated via the current messaging from the bot, so perhaps an additional note with some styling to give it emphasis will improve on the user experience.
This commit is contained in:
6
.github/workflows/manage-prs.yml
vendored
6
.github/workflows/manage-prs.yml
vendored
@ -408,8 +408,10 @@ jobs:
|
|||||||
|
|
||||||
After resolving the issue, trigger this check again by doing one of the following:
|
After resolving the issue, trigger this check again by doing one of the following:
|
||||||
|
|
||||||
- Commit the required change to the branch you submitted this pull request from.
|
- **Commit the required change to the branch you submitted this pull request from.**
|
||||||
- Comment here, mentioning `@ArduinoBot` in the comment
|
- **Comment here, mentioning `@ArduinoBot` in the comment.**
|
||||||
|
|
||||||
|
:exclamation: **NOTE**: It is not necessary to open a new pull request. :exclamation:
|
||||||
|
|
||||||
More information:
|
More information:
|
||||||
https://github.com/${{ github.repository }}/blob/main/README.md#if-the-problem-is-with-the-pull-request
|
https://github.com/${{ github.repository }}/blob/main/README.md#if-the-problem-is-with-the-pull-request
|
||||||
|
Reference in New Issue
Block a user