project-infra
project-infra copied to clipboard
kubevirt
skip-review: enable for "Sync OWNERS files by autoowners"
Is your feature request related to a problem? Please describe: Currently we need to review the OWNERS file change that is triggered by a periodic job. That's unnecessary, since the tool just mirrors the OWNERS from the source repository.
Job definition: https://github.com/kubevirt/project-infra/blob/fbb84ab7a4206079c94c1ee226a5af12915d9f0b/github/ci/prow-deploy/files/jobs/kubevirt/project-infra/project-infra-periodics.yaml#L201
Describe the solution you'd like: Use skip-review as for other automated jobs - example https://github.com/kubevirt/project-infra/pull/3937
Describe alternatives you've considered:
Additional context: Example PR: https://github.com/kubevirt/project-infra/pull/3995
@dhiller: This request has been marked as suitable for new contributors.
Guidelines
- No Barrier to Entry
- Clear Task
- Solution Explained
- Provides Context
- Identifies Relevant Code
- Gives Examples
- Ready to Test
- Goldilocks priority
- Up-To-Date
For more details on the requirements of such an issue, please see here and ensure that they are met.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.
In response to this:
/good-first-issue
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kubevirt-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.