-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Add tests:hive automatically #10563
Add tests:hive automatically #10563
Conversation
Tested on my fork -- findepi#1 . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
A question whether this works as expected.
@@ -0,0 +1,7 @@ | |||
# Pull Request Labeler Github Action Configuration: https://github.com/marketplace/actions/labeler |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that labels get added "after" the PR gets created and hence the CI run won't see the labels most probably - can we test this? (subsequent pushes would see the labels though).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this is what i expect. This automation doesn't free us from thinking.
However, oftentimes PRs do involve multiple pushes, so this may free us from doing the thing manually.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's still one issue I see - a reviewer won't know whether the hive tests actually ran just by looking at presence of label.
I'm fine with merging this provided people know of the behaviour to expect from the label.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if it is already discussed, what if we use workflow_run so that we could run this workflow could add labels and ci could use them ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's still one issue I see - a reviewer won't know whether the hive tests actually ran just by looking at presence of label.
If you see a label added after the PR is created, you must not assume it was observed by the workflow run.
But, if there was a push since label was added, then you can assume it's observed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM % comments
The labeler workflow is courtesy of Ashhar. Co-authored-by: Ashhar Hasan <[email protected]>
9f3306f
to
2cae5c9
Compare
The labeler workflow is courtesy of Ashhar.
Co-authored-by: Ashhar Hasan [email protected]