💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

The autoscroll behavior you are describing is a well-known friction point in the GitHub UI when dealing with completed workflow logs. The UI is aggressively designed to tail live logs (which is why it snaps to the bottom), but unfortunately, it doesn't gracefully disable this behavior when you refresh a completed job.

While there isn't a native toggle switch in the GitHub settings to permanently disable log autoscrolling, there are a few established workarounds to stop the jumping and reach the re-run buttons faster:

1. Use the "Summary" page instead of the job log page: If you click "Summary" on the top-left sidebar of the run, the "Re-run jobs" dropdown is always pinned at the top-right of the screen and there are no logs to autoscroll.
2. Hit Escape during page load: If you have a habit of refreshing the page and it starts to autoscroll, immediately pressing Escape will usually halt the JS scroll execution.
3. Use the 'G' keyboard shortcut: If you are dropped at the bottom of the log, simply press the g key (lowercase). It is the GitHub-native hotkey to jump to the very top of the file/log window instantly, putting the "Re-run" buttons back in view.

If you specifically want a UI change from GitHub, your best bet is submitting this as formal feedback through their Feedback portal, as this repository (community/community) acts primarily as a community discussion board rather than a direct issue tracker for the GitHub web UI engineers.