Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add GitHub Actions for closing stale issues and pull request template #2708

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

ImBIOS
Copy link

@ImBIOS ImBIOS commented Dec 4, 2024

Fixes #2698

Add a GitHub Actions workflow to close stale issues and a pull request template to ensure issues are closed when pull requests are merged.

  • GitHub Actions Workflow for Closing Stale Issues

    • Create a new workflow file .github/workflows/stale.yml.
    • Use the actions/stale@v4 action to automatically close issues that have been inactive for 30 days.
    • Set days-before-stale to 30 and days-before-close to 7.
    • Exclude issues with the pinned or security labels from being marked as stale.
  • Pull Request Template

    • Create a new pull request template file .github/PULL_REQUEST_TEMPLATE/pull_request_template.md.
    • Include verbiage like "This pull request closes #ISSUE_NUMBER" to ensure that an issue is closed when the pull request is merged.
  • Documentation Updates

    • Update CONTRIBUTING.md to include sections about the new GitHub Actions workflow for closing stale issues and the new pull request template.

ImBIOS and others added 2 commits December 4, 2024 09:49
Fixes code-charity#2698

Add a GitHub Actions workflow to close stale issues and a pull request template to ensure issues are closed when pull requests are merged.

* **GitHub Actions Workflow for Closing Stale Issues**
  - Create a new workflow file `.github/workflows/stale.yml`.
  - Use the `actions/stale@v4` action to automatically close issues that have been inactive for 30 days.
  - Set `days-before-stale` to 30 and `days-before-close` to 7.
  - Exclude issues with the `pinned` or `security` labels from being marked as stale.

* **Pull Request Template**
  - Create a new pull request template file `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`.
  - Include verbiage like "This pull request closes #ISSUE_NUMBER" to ensure that an issue is closed when the pull request is merged.

* **Documentation Updates**
  - Update `CONTRIBUTING.md` to include sections about the new GitHub Actions workflow for closing stale issues and the new pull request template.

---

For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/code-charity/youtube/issues/2698?shareId=XXXX-XXXX-XXXX-XXXX).
@ImprovedTube ImprovedTube marked this pull request as draft December 4, 2024 14:25
@ImprovedTube
Copy link
Member

hi and thank you!! @ImBIOS

  • Contributors often use github's feature to close issue from the PR (example: Add z-index for button tooltip. #2707)
  • Contributors often read latest issues first, but the number of comments and votes (thumbs) should also matter. (Github themselves moved to discussions including votes )
  • All open issues might be equally relevant. Many relevant repos have chronically too few contributors, yet there is hopes and chance to finish many of them eventually.

@peterdanwan

  • One could add a Github action to invite repeat-contributor to the organisation and the sub-group "contributors", which gives them triage rights to assign, close or label (If we cant find one such action, I think it is part of Github's API and AI can help us make that.) - Problem: If somebody bulk-removes / adds many labels, Github documents that, but there is no quick way to manage / undo that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Suggestion to clean up issues: Using GitHub Actions & Adding a Pull Request Template
2 participants