this appears due to unclosed internal check suites
the combined commit status for main is perpetually stuck in "pending". From the API, it seems GitHub Actions completes successfully, but some internal(?) check suites stay in a queued state indefinitely.
$ gh api repos/facebookexperimental/moxygen/commits?per_page=3 -q '.[] | .sha' | xargs -I {} sh -c 'echo -n "{}: "; gh api repos/facebookexperimental/moxygen/commits/{}/status -q .state'
b1d79da051d85049c4d878208c8f340ca28de1e3: pending
6e3522ccf72b76ce0843025d664076e326fb9eb7: pending
e28d16b2fcdd62661fedd9e9cebb28dbc219ca2c: pending
This breaks CLI workflows (like gh api .../status) that rely on a clean signal to automate downstream tasks.
one solution is adding something like this at the end of the GitHub workflow
- name: Set final status
run: gh api repos/${{ github.repository }}/statuses/${{ github.sha }} -f state='success' -f context='ci/combined-signal'
this appears due to unclosed internal check suites
the combined commit status for main is perpetually stuck in "pending". From the API, it seems GitHub Actions completes successfully, but some internal(?) check suites stay in a queued state indefinitely.
$ gh api repos/facebookexperimental/moxygen/commits?per_page=3 -q '.[] | .sha' | xargs -I {} sh -c 'echo -n "{}: "; gh api repos/facebookexperimental/moxygen/commits/{}/status -q .state'This breaks CLI workflows (like gh api .../status) that rely on a clean signal to automate downstream tasks.
one solution is adding something like this at the end of the GitHub workflow