Hi! I need help with the Github Workflows, 0% of t...
# how-do-i
r
Hi! I need help with the Github Workflows, 90% of the time nothing runs, I get this: Checks in progress... 0 of 6 completed - 6 required checks It's very common when updating a PR deep down, the ones above don't trigger a run The cancel/rerun button won't do much The solution I currently have is to git push nothing then submit to trigger another workflow run, it's not ideal I would expect the cancel/rerun to work I tried triggering a workflow to rerun manually but Graphite doesn't get its status, cmd:
gh run rerun {prev_workflow_id}
p
(If applicable) To help us more clearly understand what you're trying to do, please provide additional details about: - Screenshots / debug logs / list of commands you've tried to run so far - Your workflow - Current state
hey Romain, when this happens and you look at the PR in GitHub do you see the checks as having completed? Sometimes they get stuck in GitHub with a message like "waiting for status to be reported". In these cases, if the re-run jobs button does not trigger a rerun of these checks then pushing a change to the PR to force GitHub to rerun the checks is recommended, as you do.
r
is cancel/rerun available from the CLI?
I could script everything and kill a rogue workflow if needed
p
no there isn't a CLI command to perform that
r
can I use the CLI token to call the api?
p
in theory yes, but in practice the API endpoints are not intended for public consumption outside of
gt
or Graphite web app operations.
r
before, pushing an actual file... everything works then a branch below is updated, this happens: Romain changed the base branch from 10-20-banner_components to graphite-base/9375 Romain force-pushed the 10-20-banner_-_viewer branch from
d8d72a4
to
7e818ea
Romain force-pushed the graphite-base/9375 branch from
33097d4
to
bb0613b
Romain changed the base branch from graphite-base/9375 to 10-20-banner_components no action is triggered, nothing is pending github side
there should be one button to cancel & one button to run do the magic on your end, it's expected to work as intended
p
Ah the behavior you're seeing there is the automatic rebasing.
For configuring recommended CI settings, we have this note for ensuring that CI is running on upstack branches
r
we do have the same settings on the yaml I don't have access to the optimization page yet, it should be set exactly like that, right?
p
Do you have one of the types in the job trigger as
synchronize
?
Copy code
pull_request:
    types: [
        # Default pull_request trigger types.
        opened,
        synchronize,
        reopened,
      ]
Adding the
synchronize
event should handle base branch changes
r
yes we have that