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
[Merged by Bors] - feat: add lake exe shake
to CI
#9751
Conversation
920af90
to
3915f97
Compare
a529ea8
to
699b03d
Compare
I think we need more straightforwardly human readable output. e.g.
should become:
|
I was hoping people would be using the github annotations, which are a bit more user friendly. The CLI output is more optimized for batch usage, where that kind of verbosity is a bit overwhelming if there are 30-100 of them. You can also just ignore the CLI output entirely and use |
Can we turn this into clickable suggestions like we have for some style linters? Or it will fail because github won't accept suggestions to the lines that aren't touched by the PR? |
That's definitely not something a user newly encountering |
What does |
|
I think we either need to have human readable output, or entirely suppress the non human readable output from the CI logs when you click on a red X! How is a new contributor meant to know they are meant to ignore this output? |
Does #9996 address your concerns? (The output is of course human readable and useful, so I definitely would not want to suppress it, it's just not exactly intended to be a tutorial about itself. Most other CI logs are at a similar level of verbosity.) |
This disables batching for this PR, so that it doesn't race with other PRs: bors single on |
This PR/issue depends on: |
Thanks 🎉 If CI passes, please remove the label bors d+ |
✌️ digama0 can now approve this pull request. To approve and merge a pull request, simply reply with |
bors r+ |
Pull request successfully merged into master. Build succeeded: |
lake exe shake
to CIlake exe shake
to CI
shake
bug, improve noshake.json generation #9772This checks files for unused imports. The output here is piped through
gh-problem-matcher-wrap
so that it will show up as annotations.