-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[CI] Running /fix:cmd
over a PR rebuilds but skips GH action checks
#4339
Comments
This discussion links to the official GH documentation about the topic:
And:
Using a PAT seems to be a reasonable solution for me. |
We have one already, and maybe using it consistently will help. Let me raise a PR for that. |
So the "good" news is that we are not the only ones running in those issues, so there is some info out there that is helpful, but this is a rabbit hole, looks like the checkout action adds additional trouble: |
@svrnm - we're hitting permission issues now, see https://github.com/open-telemetry/opentelemetry.io/actions/runs/8822774576/job/24221719586: |
@chalin that's odd because this step was not updated by any of the 2 latest changes: |
Reverting the last change, as you did was what I had in mind too. Thanks for doing that and investigating further 🙏 |
I am worried we are in a position where neither token gives us all the things we need, as it looks like the PAT is not allowed to push to forks. In my research I came across a page that listed solutions to this problem but I closed it so I have to find it once again will keep you posted. |
For context, see:
Unless we get a separate bot to handle
/fix:*
commands, we're stuck with this behavior: GH doesn't rerun actions if a workflow over the same repo committed a change to a PR. I usually work around this by forcing a change (via rebase, or by making a trivial edit) over the PR, but that isn't always practical.Other possible solutions:
/fix:*
commands so that GH runs the full action checks. (This would be a lot of work but might be worth it in the long run.)main
branch. (This is easier to setup, and will at least notify us if build checks are broken).Thoughts @open-telemetry/docs-maintainers?
The text was updated successfully, but these errors were encountered: