-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
GitHub workflow output format #10260
Labels
Documentation 📗
Needs PR
This issue is accepted, sufficiently specified and now needs an implementation
Comments
I'd be happy to provide a patch myself, if that were helpful 😃 |
Hey @codingjoe, we have that already (example, release note), but clearly we need some docs to make it more discoverable. |
If we do #4322, the discoverability would be great. |
codingjoe
added a commit
to codingjoe/pylint
that referenced
this issue
Mar 10, 2025
@jacobtylerwalls thanks mate 🥇 I could have just tried |
Pierre-Sassoulas
pushed a commit
that referenced
this issue
Mar 10, 2025
Pierre-Sassoulas
pushed a commit
that referenced
this issue
Mar 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Documentation 📗
Needs PR
This issue is accepted, sufficiently specified and now needs an implementation
Current problem
Hi there 👋,
GitHub supports a special output format for workflow, that enables the workflow to create code comments on pull-requests.
We currently use a GitHub workflow similar to this:
However, this will cause PyLint to run multiple times, wasting precious compute time.
Desired solution
I'd love to native support
--output-format=github
that correctly sets the message type for GitHub. This is the only thing, that you currently can't achieve with--message-template
.Since GitHub is a rather popular collaboration platform, I believe this feature would be welcome by other community members 😉
Additional context
https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions
The text was updated successfully, but these errors were encountered: