Hi Rain, +1 on this proposal.
I suggest we consider using *GitHub Actions* to automate these tags. For example, it would be very efficient if the workflow could automatically remove status: needs-update (and add waiting-for-review) whenever a contributor pushes a new commit. This would ensure the status is always up-to-date without manual intervention. Best regards, Jian Wang (WangzJi) Rain Yu <[email protected]> 于2025年12月25日周四 16:38写道： > Hello everyone, > I’m writing to propose adding a set of PR management tags prefixed with > status: to our repository, aiming to streamline the tracking, review, and > resolution process of Pull Requests. The detailed definitions of these tags > are as follows: > > 1. status: ready-to-merge: This tag indicates that the PR is fully > polished and meets all merging criteria, waiting for the maintainers to > complete the merge operation. > 2. status: needs-another-reviewer: This tag means one of the members > with write access to the repository has finished reviewing the PR, but > an > additional reviewer is required to ensure the code quality and logic > validity. > 3. status: waiting-for-review: This tag is applied to all newly > submitted PRs by default, representing that no reviewer has started the > assessment work yet. > 4. status: needs-update: This tag is assigned when a committer or PMC > member has reviewed the PR and identified actual issues. Though the PR > cannot be merged temporarily, it is of potential value and only needs > targeted revisions to meet the standards. > 5. status: needs-discussion: This tag suggests that the PR has been > reviewed, but there are still unresolved questions or controversial > points > that require further discussion among the team to determine the next > steps. > > I sincerely hope you can share your thoughts and feedback on this proposal. > Later, I will submit an official issue in the repository for in-depth > discussion. > Thank you for your attention and support! > Best regards,Rain Yu >
