[2025-04-09] Incident Thread

[github-actions[bot]]

❗ An incident has been declared:

Disruption with some Pull Requests stuck in processing state

Subscribe to this Discussion for updates on this incident. Please upvote or emoji react instead of commenting +1 on the Discussion to avoid overwhelming the thread. Any account guidance specific to this incident will be shared in thread and on the Incident Status Page.

[github-actions[bot]]

Update

Some users are experiencing delays in pull request updates. After pushing new commits, PRs show a "Processing updates" message, and the new commits do not appear in the pull request view.

---

Relevant stamps: dotcom

[Koagonzalo]

Good

[github-actions[bot]]

Update

The team has identified a mitigation and is rolling it out while actively monitoring recovery

---

Relevant stamps: dotcom

[github-actions[bot]]

Incident Resolved

This incident has been resolved.

[Marcono1234]

Was this only resolved for new pull request actions?

Because multiple hours after this was marked as resolved my pull request moditect/moditect#260 still showed "Processing updates".

Now it does not show "Processing updates" anymore, but the updates still weren't processed. The pull request still shows f6e20d1 as latest commit, even though I had force-pushed yesterday and the latest commit should now be d01a252 instead (the GitHub UI for my fork shows that properly).

Edit: I ended up force pushing again, and that updated the PR. Though I am wondering how many users are still affected by this without knowing it, and how GitHub behaves when you try to merge a PR with unprocessed changes.