Pushed changes take a long time (1-3 minutes) to appear on the pull request

[domdomegg]

Select Topic Area

Bug

Body

This is a bit of an odd one. I've been using GitHub for a long time, and am used to doing a git push and seeing my changes appear on my PR quickly (e.g. within a few seconds). Recently, I've found the gap between pushing and the changes appearing on the PR getting longer, sometimes up to 1-3 minutes.

Having this time be short is important to me as:

• I can push, then tell reviewers I've made the changes. Recently, I pushed and commented that I had addressed some feedback on a PR comment - but then the reviewer couldn't see the changes and was confused. I don't want to wait a couple minutes for my changes to appear before being able to move onto commenting on their feedback.
• I want to know my changes have been saved, in case I'm in a hurry to get going somewhere but don't want to risk losing changes
• I want to confirm that CI is running, again so if I want to kick off a time-consuming build and go do something else I can be sure it'll be done by when I'm back.
• If it's an urgent hotfix that I'd like to release quickly, I don't want extra delays getting it merged it into the default branch and released. I could enable pushing directly to the default branch, but this feels more like a workaround and is often not suitable for all workflows/org security guidelines - and means I can't run CI on a branch first.
• If it's pushing a new branch, I want to find it in the UI to create a pull request - not have to wait a couple minutes (either waste time, or incur the overhead of context switching to a different task / having to remember to come back to create the PR).

To help narrow this bug down a bit:

• This is on GitHub.com
• The actual git operation seems to occur fine (i.e. my terminal says everything is complete within a second or two), so it likely happens after GitHub has recieved the data and is processing it.
• Doing a hard refresh in the browser does not make my commit appear, so it doesn't seem to be a browser-side caching issue.
• This is transient: sometimes changes load quickly fine, othertimes there's quite a delay.
• This happens on both big and small PRs too: this has happened on PRs of ~100 lines, and single line commit changes.

[Sebastian-Brud-Tectonic]

I would say it takes even more than that.

1. My colleague opened a PR more than 24hrs ago
2. I opened it and reviewed. Left comment on what should be changed
3. He committed it
4. I kept refreshing PR page (on github.com - Google Chrome browser) in order to see what changed (I did not wait for "Refresh" button to appear)
5. I kept seeing the same commit content (for 24 or more minutes)
6. I jumped to the most recent commit
7. PR "Changes" tab content changed

[ravitejaroyal]

@domdomegg , did you able to find out any new information regarding this issue ?

[domdomegg]

No, I have not recieved any extra information

[paulaatsnyk]

A colleague and I are experimenting these delays too. Is there any solution to the issue? 🙏

[SanderLam]

https://www.githubstatus.com/ is showing that there currently is an issue with commits showing up on PR's. I have the same issue.

[adityaparab04]

Stuck on the same issue for past 15 minutes. Do I have to reset the Head and re-commit the requested changes to the PR or Is there any other fix to this problem?

[Fraih001]

Also experiencing this issue, currently. Seems to happen every once in awhile, but eventually, things start to speed up again...

[eddfigarola]

This is happening Today again

[crimsonhawk47]

For us, it appears the workaround is to look directly at the branch and view the most recent commit. Our changes didn't show up for hours until someone did this.

[simonerlandsen]

Happening for us right now. @crimsonhawk47 tip seams to do be a work around that triggers the PR to update

[robertogvieira]

happened to me this morning for the 1st time ever and only realised it hours later, after some confusion looking at missing commits on my PR, lol.
Turns out it was due to an incident and I'd pushed the changes right by the time the incident was identified.

[timonmasberg]

Closing and reopening the PR worked for me... pretty annoying bug tho.

[mssodhi]

This fixed it for me! Thanks