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

Enable milestone and milestoneapplier plugins for Prow #807

Closed
tuminoid opened this issue Jul 3, 2024 · 6 comments · Fixed by #895
Closed

Enable milestone and milestoneapplier plugins for Prow #807

tuminoid opened this issue Jul 3, 2024 · 6 comments · Fixed by #895
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@tuminoid
Copy link
Member

tuminoid commented Jul 3, 2024

Enable milestone and milestoneapplier plugins for Prow to automatically assign a milestone to closed PRs, and allow milestone setting for project members in case they cannot do it via the menu.

We should grab config for this from CAPI, with the notable difference is that we have many repos, different milestones in them, and some repos do not have milestones at all.

https://prow.k8s.io/plugins

@metal3-io-bot metal3-io-bot added the needs-triage Indicates an issue lacks a `triage/foo` label and requires one. label Jul 3, 2024
@tuminoid
Copy link
Member Author

tuminoid commented Jul 3, 2024

@Rozzii FYI

@Rozzii Rozzii self-assigned this Jul 3, 2024
@Rozzii
Copy link
Member

Rozzii commented Jul 3, 2024

/triage accepted
/kind feature

@metal3-io-bot metal3-io-bot added the triage/accepted Indicates an issue is ready to be actively worked on. label Jul 3, 2024
@metal3-io-bot metal3-io-bot added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 3, 2024
@metal3-io-bot metal3-io-bot removed the needs-triage Indicates an issue lacks a `triage/foo` label and requires one. label Jul 3, 2024
@Rozzii Rozzii moved this from Backlog to MISC WIP in Metal3 - Roadmap Jul 3, 2024
@metal3-io-bot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 1, 2024
@tuminoid
Copy link
Member Author

tuminoid commented Oct 1, 2024

/remove-lifecycle stale
/lifecycle frozen

@metal3-io-bot metal3-io-bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 1, 2024
@tuminoid
Copy link
Member Author

tuminoid commented Nov 7, 2024

@lentzi90 this one we discussed offline

@lentzi90
Copy link
Member

lentzi90 commented Nov 7, 2024

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
Status: Done / Closed
Development

Successfully merging a pull request may close this issue.

4 participants