Home feed is not useful

[stuartromanek]

Select Topic Area

Comment

Body

Not useful at all. This isn't social media, I don't come here to be idle. Why are the repositories I actually work on de-prioritized in the left sidebar? This screen should be full of relevant links and highlights about the things I am touching.

[PimpOfSune]

I came here to post bugs to already-known-to-me projects and get help from said projects' maintainers.
I need a goddamn issue tracker consisting of my issues, not a hodge-podge from random repos.

[LiteBrite82]

Hi @PimpOfSune
Thats a great use case for Feed; I'll mark this as product feedback.

In the meantime, you could use an issue search. I use one to find all of the issues having to do with me that may have fallen off of my radar: state:open mentions:@me involves:@me sort:updated-desc repo:<optional> -assignee:@me

You could modify this with label:bug if the bug issue you submit gets labeled as "bug", or just add "bug" to the end of your search (if you added the word "bug" to the issue you created).

Try: state:open mentions:@me involves:@me sort:updated-desc label:bug "bug"

This should return every issue that involves or mentions you that has a bug label and the term bug starting with the most recently updated issue in descending order. (remove label:bug for a broader search - incase maintainers dont label bug reports)

You can also save this search string by clicking the save button under the right hand side of the search bar.

Recall the saved search string by typing saved:<whatever you named the saved search>

Feel free to repost your comment as a new discussion over at Projects and Issues; The community may have other creative means of helping your workflow.

[LiteBrite82]

Now that I step back a bit; I totally overcomplicated this "bug" state:open author:@me sort:updated-desc is way more efficient.

[PimpOfSune]

Yes, yes, I'm acquainted with the concept of custom dashboards, been there, done that way before JIRA migrated everyone to design which they erroneously consider as "modern AND convenient".

If virtually anyone have to make a custom dashboard - maybe it's time to make things official and introduce it.

What specifically ticks me off with this specific product feedback is not even necessity to take matters into my own hands for me meself.

What ticks me off is that some person in good health, in sound mind, and with skills&accomplishments serious enough to make him acknowledged as "worthy for making decisions THAT big" decided that one of building blocks of productive development - an issue (of whatever type it could be) - is unworthy of its dedicated dashboard in:

• user profile https://github.com/PimpOfSune
  (we only see some posted/participated issues in Overview > Activity Log there)
• user's "personal menu" which is being opened by a click on avatar at top right corner
  (Your Issues where? and why Your Copilot is more important than Your Issues?)
• on GitHub's frontpage https://github.com/ also known as https://github.com/dashboard
  (this very issue Home feed is not useful #138509 is basically about some random junk (ergo "Recommended for you" & "Explore repositories", both of which, for some incompherendable reason, are proposing me a dang NelloKudo / osu-winello repo for a looksie) being SO important so it's impossible to disable it, while really crucial info which is needed everyday is living in a sidebar ghetto)
• at https://github.com/issues , in which I need to be able to see issues I've engaged with, like Civilization VI always launches DX12 version from system tray quick launch menu (does not respect launch options) ValveSoftware/steam-for-linux#11252
  (I won't count it as a dashboard proper if instead of convenient filterint it gives HINTS on how POSSIBLY common filtering can be implemented. With RANDOMIZED hints, thank you very much
  
  Now I know what "comments:>50" does - and still have 0 idea on how to just grab a list of issues with which I was engaged in)
• and so on, and so on, and so on.

Well... at least people who, unlike us bug reporting plebs, are actually doing something useful (read: writes code, commits it, etc-etc) have a dedicated dashboard for... pull requests? commits? other important building blocks of effective useful open-source software?
Well, I'm probably not skilled enough to justify if a dashboard of pull requests (which, thanks gods, exists somewhere) is less worthy to be present on homepage either.
"Recommended for you" + "Explore repositories" feeds are probably so much more important than dashboard with pull requests either.
But that person which, in good health, in sound mind, and with skills&accomplishments serious enough to make him acknowledged as "worthy for making decisions THAT big", decided that pull requests dashboard not as important either probably knew what they were doing.

---

What I'm leading this rant to is, there was a Goddamn Good Reason to make things into what we currently have.

Either I as end user am failing to grasp the real needs I have - so suggested separate discussion will be pointless.

OR the person which ordered it look&work this way is due for reassessment of his skills and accomplishments. In this case a separate discussion won't do good either as it's a headache for completely different crowd of people which have to have keen interest in GitHub actually being useful.

---

(not mentioning that for average John Doe all that stuff with custom dashboards is a witchcraft.
Average John Doe don't have my experience.
Average John Doe needs possibility to post bug reports and other concerns - and to check his reports working out of the box.
Assuming that engagement of average John Doe with projects hosted at GitHub is a use case viable for GitHub's current owners.
My intent was to include Barotrauma's issue tracker https://github.com/FakeFishGames/Barotrauma/issues as exemplar of bug-reporting-for-john-does - but, apparently, something became utterly broken there so they had to use Discussions https://github.com/FakeFishGames/Barotrauma/discussions/categories/bug-reports as a crutch instead.
Which is alarming... apparently, I will be unable to check issues which I could post for Barotrauma anymore with Issues dashboard because - cue excited drumrolls - bug reports go to Discussions which are not Issues now!
Golly... At least I know that NelloKudo / osu-winello repository exists now. Thanks GitHub!)

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