Display Order Issue in GitHub Homepage Activity Feed

[chenmingyong0423]

Select Topic Area

Bug

Body

I’ve observed an issue with the activity feed on the GitHub homepage. While the feed correctly retrieves the latest updates based on time, the display order is ascending (oldest updates at the top, newest updates at the bottom) instead of descending.

This makes it less intuitive to quickly view the most recent updates. Additionally, I noticed that the filter list does not provide any option to sort the feed, which leads me to believe this might be a bug.

[github-actions[bot]]

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

[marius-sucan]

Today, out of blue , my feed is no longer in chronological order. Why? How to get it back to be in chronological order?

[whitews]

Came here to post the same issue. Started seeing this sometime within the last 12 hours

[troysjanda]

Came here to post the same issue. Since this AM 12/05/2024 I am seeing stuff from weeks to months old at the top and the newest stuff at the bottom or after clicking the load more call to action button, please revert to newest 1st.

[spenserblack]

And it looks like "load more" will load older events (as expected), but then continue to sort oldest-to-newest, so that the ordering of the entire feed is like this:

1. 2 months ago
2. 1 month ago
3. 1 week ago
   • load more here
4. 3 months ago
5. 2 months ago

Which makes the ordering just stop making sense, so definitely looks like a bug.

[troysjanda]

I see months old stuff listed 1st and the newest at the bottom or after clicking the load more since yesterday. I want the newest stuff 1st, dont need to scroll thru a long feed to get to the newest stuff makes no since

[grasmanek94]

same issue here, 2 months ago is at the top and last week it at the bottom.

[warrengalyen]

Same issue. Just noticed today that my feed is sorting from oldest to newest now instead of newest to oldest.

[dmadisetti]

If this is an algo feed, I really hope you keep listening to your users and revert it (or provide the option)

Github is a tool, not twitter

[PRO-2684]

Same issue here. Placing the latest activity at the bottom just don't make sense.

[PRO-2684]

Seems that it is fixed.

[callbacked]

Same issue here, both on the desktop site and iOS app.

[risv1]

Same issue here.

[whiteSHADOW1234]

looks like it’s been fixed today by reverting to newest-to-oldest chronological sorting.

[chenmingyong0423]

yep

[chenmingyong0423]

Seems that it is fixed.