Add Dart PR health workflow #6803
Conversation
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback. |
There was a problem hiding this comment.
do we really need this? we don't currently use any actions that post to PRs
There was a problem hiding this comment.
This is a Github restriction, see https://securitylab.github.com/resources/github-actions-preventing-pwn-requests/
There was a problem hiding this comment.
I mean do we really want to post summaries
There was a problem hiding this comment.
Github doesn't allow for warnings, only failures or successes. In the case we don't want to post to PR comments, I would suggest to turn all warnings into failures. This then requires to add labels to skip checks if one wants to ignore the warning.
| @@ -33,6 +33,7 @@ on: | |||
|
|
|||
| permissions: | |||
| contents: read | |||
| pull-requests: write | |||
Add workflow for PR health, checking things like breaking changes, missing exports etc.