-
Notifications
You must be signed in to change notification settings - Fork 3.7k
use the_crawl-based package reviewer #9246
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
|
This is really good actually, using your latest version of the reviewer. I think it has all the output I'd want.
So, as a user of this thing I really want this :D I hope you and Fichte can work out how to manage the repo. IMO I can continue to just use your fork here. The old package test action also did not really depend on his repo anyway. |
|
It becomes easier to decipher when you just have one job(?) per action(?) / file. I may just merge into the forked main which is easier to use and to see and remember. |
|
Where it says "CHECK," is it possible to (also?) include the name of the package being tested? |
|
Why shouldn't that be possible, it's computers. But I also have a question: @braver, can you just set in the workflow here, and I write a PR comment. |
961274b to
d9ffc1a
Compare
Add a new job 'crawl_package' to review package changes on pull requests and specific issue comments.
ce55a97 to
f726243
Compare
|
📦 |


No description provided.