New commit takes 1-2 hours to actually commit to repo #148408
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Body
We are seeing an issue where a new commit is taking 1-2 hours before it shows on the web and is downloadable via fetching origin from another computer where the commit did not take place. The changelog for the commit is immediately shown. The integrated CI/CD pipeline to deploy the code is triggered but does not use the updated commit due to this delay.
Beta Was this translation helpful? Give feedback.
All reactions