You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When it's run on a PR, GitHub status reporting fails to work at all. I think what happens is that, the autofmt becomes the latest commit on the PR and status reporting switches to that commit, but because one action can't trigger another indirectly, the normal CI steps don't retrigger on the new commit, leaving them as zombies on the main PR commit.
The text was updated successfully, but these errors were encountered:
alecthomas
changed the title
Run autofmt on main
Run autofmt on main instead of PR
Mar 13, 2024
for issue: #1075
Not sure of best way to test - I may try it on another branch perhaps?
edit: tested it by having it push to this branch as if it was main, and
it did what I expected. Doesn't need the FTL_AUTOFIX_TOKEN anymore, and
won't trigger a rebuild (flip side of that is if it does have a rebuild,
there won't be a build run against it - is that suitable @alecthomas ?)
---------
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
When it's run on a PR, GitHub status reporting fails to work at all. I think what happens is that, the
autofmt
becomes the latest commit on the PR and status reporting switches to that commit, but because one action can't trigger another indirectly, the normal CI steps don't retrigger on the new commit, leaving them as zombies on the main PR commit.The text was updated successfully, but these errors were encountered: