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

Don't remove "full tests required" label when PR is created with it #15028

Closed
ashb opened this issue Mar 26, 2021 · 5 comments
Closed

Don't remove "full tests required" label when PR is created with it #15028

ashb opened this issue Mar 26, 2021 · 5 comments
Labels
area:dev-env CI, pre-commit, pylint and other changes that do not change the behavior of the final code kind:bug This is a clearly a bug kind:feature Feature Requests

Comments

@ashb
Copy link
Member

ashb commented Mar 26, 2021

Right now we have some process/part of the CI pipeline that is removing the "full tests required" label from newly created PRs. #15022 (comment)

This only applies to committers/PMC who can choose to apply this label to a PR (non committers can't control labels) but in this case we shouldn't remove the label.

@ashb ashb added kind:bug This is a clearly a bug area:dev-env CI, pre-commit, pylint and other changes that do not change the behavior of the final code labels Mar 26, 2021
@potiuk
Copy link
Member

potiuk commented Mar 26, 2021

It gets removed when the Image is not in "removed" state

The current process is that label is not really supposed to be "manually" set - it is set automatically when we determine that the PR "likely" needs full tests and after it gets approved by a committer. If it gets "deapproved" it looses the label. We might want to change it that once the label is set (whether automated or manual) it can only get removed manually. That might be actually a nice improvement of the current workflow.

@potiuk potiuk added the kind:feature Feature Requests label Mar 26, 2021
@ashb
Copy link
Member Author

ashb commented Mar 26, 2021

I've been setting it manually as an optimization (for instance when I know a change will need full tests.) to avoid a second test run. I thought this used to work, but I'm not 100% sure.

In this case it didn't get unapproved, it was just never approved :).

@potiuk
Copy link
Member

potiuk commented Mar 26, 2021

Yeah. to be precise the label is automatically removed now when the PR has no "Approved" status (non-approved also falls in this category :) ). It think @TobKed that would require slight change in the action of yours ?

@potiuk
Copy link
Member

potiuk commented Mar 26, 2021

PR created in @TobKed 's action: TobKed/label-when-approved-action#6

@eladkal
Copy link
Contributor

eladkal commented Oct 13, 2021

@potiuk this is solved, right?

@potiuk potiuk closed this as completed Oct 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:dev-env CI, pre-commit, pylint and other changes that do not change the behavior of the final code kind:bug This is a clearly a bug kind:feature Feature Requests
Projects
None yet
Development

No branches or pull requests

3 participants