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

[Feature Contribution]: Automatically remove "Ready for review" label on closed PRs or Issues #476

Open
2 tasks done
danuw opened this issue Feb 27, 2024 · 2 comments
Open
2 tasks done
Assignees
Labels
devops Identify issues that impact delivery lifecycle as opposed to functionality (~basically code changes) stale

Comments

@danuw
Copy link
Collaborator

danuw commented Feb 27, 2024

What happened?

Create a workflow to automatically remove "Ready for review" label on closed PRs or Issues
so that ready for review only surface items that are relevant

Code of Conduct

  • I agree to follow this project's Code of Conduct

Feature Commitment

  • I commit to contributing this feature as a PR and working with the GSF to merge this feature into the Carbon Aware SDK.
@danuw danuw added the devops Identify issues that impact delivery lifecycle as opposed to functionality (~basically code changes) label Feb 27, 2024
Copy link
Contributor

This issue has not had any activity in 120 days. Please review this issue and ensure it is still relevant. If no more activity is detected on this issue for the next 20 days, it will be closed automatically.

Copy link
Contributor

This issue has not had any activity in 120 days. Please review this issue and ensure it is still relevant. If no more activity is detected on this issue for the next 20 days, it will be closed automatically.

@github-actions github-actions bot added the stale label Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops Identify issues that impact delivery lifecycle as opposed to functionality (~basically code changes) stale
Projects
Status: Todo
Development

No branches or pull requests

2 participants