You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This feature aims to automate the closure of old pull requests (PRs) within repositories. As software projects progress, PRs often accumulate, some of which become outdated or irrelevant over time. Manually managing these outdated PRs can be time-consuming and inefficient for repository maintainers.
The proposed feature would enable repository administrators to set criteria for automatic closure of PRs based on factors such as age (e.g., PRs older than three months), activity (e.g., no updates or comments within a specified timeframe), or label status (e.g., PRs labeled as "stale"). Once configured, the system would periodically scan the repository for PRs meeting the specified criteria and automatically close them, notifying relevant contributors and stakeholders of the closure.
This automation would streamline repository maintenance, ensuring that active PRs remain in focus while reducing clutter and confusion caused by outdated ones. Additionally, it would encourage contributors to keep their PRs up-to-date and relevant to the current state of the project.
Add ScreenShots
NA
Record
I agree to follow this project's Code of Conduct
I'm a GSSOC'24 contributor
I want to work on this issue
The text was updated successfully, but these errors were encountered:
Describe the feature
This feature aims to automate the closure of old pull requests (PRs) within repositories. As software projects progress, PRs often accumulate, some of which become outdated or irrelevant over time. Manually managing these outdated PRs can be time-consuming and inefficient for repository maintainers.
The proposed feature would enable repository administrators to set criteria for automatic closure of PRs based on factors such as age (e.g., PRs older than three months), activity (e.g., no updates or comments within a specified timeframe), or label status (e.g., PRs labeled as "stale"). Once configured, the system would periodically scan the repository for PRs meeting the specified criteria and automatically close them, notifying relevant contributors and stakeholders of the closure.
This automation would streamline repository maintenance, ensuring that active PRs remain in focus while reducing clutter and confusion caused by outdated ones. Additionally, it would encourage contributors to keep their PRs up-to-date and relevant to the current state of the project.
Add ScreenShots
NA
Record
The text was updated successfully, but these errors were encountered: