-
Notifications
You must be signed in to change notification settings - Fork 44
Run PR depenecy check on every comment added to PR #216
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
Conversation
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.
Nice 👍
Though maybe every comment is still a lot, since it will spin up a VM every time? shall we have a trigger word instead? |
We may, like in napari/napari#6101. What phase did you suggest? |
Yeah better. Something like "dependency closed"? |
Maybe just "dependency"? |
Though it will fire if we talk about library dependencies xD |
hm. Maybe? I do not know. but it is now easy to suggest proper phase by "request changes" |
would |
deps can also be issues in principle I think... I think we're being overzealous here, let's just merge and if problems arise we can solve them :P |
@Czaki please update description first! |
@brisvag updated description |
Description
For the current state, the core dev needs to restart the dependency check, or a dummy commit needs to be done.
As the PR dependency check is cheap, I think it is worth triggering it on every comment, so if a user write comment containing
merge
the check will be restartedType of change
References
https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_comment-use-issue_comment