Skip to content
This repository has been archived by the owner on Jun 27, 2022. It is now read-only.

Do not re run qeb hwt at each event #140

Closed
pacospace opened this issue Jan 21, 2021 · 6 comments
Closed

Do not re run qeb hwt at each event #140

pacospace opened this issue Jan 21, 2021 · 6 comments
Labels
human_intervention_required kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@pacospace
Copy link
Contributor

Describe the bug
Do not re run qeb hwt at each event

To Reproduce
Steps to reproduce the behavior:

  1. Change title in PR?

Expected behavior
Check run is not rerun at each event (change title of PR)

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

@goern
Copy link
Member

goern commented Jan 21, 2021

what is the question or proposal here?!

@pacospace
Copy link
Contributor Author

what is the question or proposal here?!

For example when the title of the PR is modified qeb-hwt restarts. I don't expect that to happen. The idea would be if possible to filter events like that to avoid re triggering the check run. wdyt?

@sesheta sesheta added kind/bug Categorizes issue or PR as related to a bug. and removed bug labels Jan 28, 2021
@sesheta
Copy link
Member

sesheta commented Apr 28, 2021

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

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 28, 2021
@sesheta
Copy link
Member

sesheta commented May 28, 2021

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

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 28, 2021
@sesheta
Copy link
Member

sesheta commented Jun 27, 2021

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@sesheta sesheta closed this as completed Jun 27, 2021
@sesheta
Copy link
Member

sesheta commented Jun 27, 2021

@sesheta: 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/test-infra repository.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
human_intervention_required kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants