Open sophia-guo opened 4 years ago
@karianna notice that you did a quick and great job of labelling. Are you using any other mechanism?
@sophia-guo - I believe some of the labeling you are noticing is done via project automation that @karianna setup (when new issues are opened, they are automatically added to the TODO column of our openjdk-tests project).
It's partly that and I do a daily sweep of all open items as well :-). One of the challenges is that GitHub's support for this improved over time but you can't migrate projects to the 'newer' automation process :-(.
We do appreciate your daily custodial sweep, thanks @karianna !
I see it's project boards. Good to learn that!
I think we are in agreement that the 2 suggested 'helper' workflows would be of benefit, especially the stale issues one... given I am manually reviewing older issues to see if I can close them. We should either include these or close this issue as won't fix.
To automate and improve efficiency of the project we are thinking to enable a set of GitHub Actions. GitHub Actions allow unlimited minutes for workflows on open sourced projects, which could automate common tasks easily.
Examples:
Close Stale Issues and PRs uses a cron job to look through all issues/PRs in the repository and if the issue/PR has not been modified for a period of time, it adds a stale label (configurable) to the issue/PR and optionally comments on the issue.
If the stale label is present for an additional amount of time, the issue/PR is eventually closed.
This Action helps to maintain the number of issues/PRs on the repository which can easily get out of hand. The common scenario is someone opening up a WIP: PR and never completing it, but not closing the PR off. Or for example opening up an issue to ask a question and then not closing the issue once the answer is posted. Such issues clutter the queue needlessly and give the appearance of "too many problems" or "too big of a queue to get something contributed" on the repository.
The automation can be overridden by either a committer removing the stale label, or any contributor simply commenting on the issue/PR.
Pull Request Labeler triages PRs based on the paths that are modified in the PR.
Examples: https://github.com/sophia-guo/openjdk-tests/pull/1
We could also create our own actions to fit the specific requirement. This is open discussion and could be a general discussion in the AdoptOpenJDK community.