Opting out just makes the Feed appear on / again. I'd rather they just give you the option instead of doing the opt-out-until-we-remove-the-opt-out thing, the coward's way to change a default.
Or are you saying that all those things are new in the "new dashboard", compared to how that was initially when they launched the preview?
https://github.blog/news-insights/product-news/github-code-s...
Improvements to Projects have been really good. Personally, I find no need for external project management tools anymore.
The issues and projects team(s?) have been cooking.
I know it's frowned upon to ask this here, but: did you read the article (or open GitHub) before posting this comment?
This seems to push your issues and pull requests as the main items of the page, and that's significantly better.
Complaining might work, but continuous complaining is tiresome.
Pretend that there is a different set of people complaining about this change than the last one, and that common to both sets are people who don't think either are good.
A list of tasks I'm already behind on is the last thing I want to be reminded of constantly.
:)
Maybe we aren't at the bottom of the pile of trash, but we are still in a pile of trash. It's a page that, objectively speaking, doesn't work like it says it does. Things simply do not work. This isn't a "I don't like it" problem. This is the page literally says one thing and does the opposite.
And yes, it "seems" to push your issues and PRs as the main items of the page. Keyword there is seems. Nothing on that new page helps me work on the projects I'm working on. But there is a PR I opened for my project back in Jan still open on that page? And more importantly, no way to resolve it from that page?
No real developer designed this. It's trash. Maybe not the bottom of the heap, but it's still trash. I'd be ashamed to put this out.
> but the last iteration had Copilot at the top
It still does. And for some reason, when you start typing, you aren't typing in that chatbox. Instead... you start typing in search even though search has a / to type there.
It's bad. It's really bad. And so much wasted space. I'm sorry, but expect some level of quality. Don't just accept trash that literally doesn't work.
If this is the new default, can we get rid of the blue dot in the top right now?
And with the gh cli, I dont even need to visit the overloaded github website anymore for PRs, Issues, Discussions etc, I can read it write in my terminal with pure text, no nonesense in it, clean and minimal, exactly what I need to be productive - and like you said, no context switching.
P.S.: It also feels like I am living in those futuristic 80/90s Cyberpunk Animes and Mangas where everything was a terminal/tui B-)
Just this week, I encountered the following problems:
- a diff showing "0 files changed" while there are many [1];
- suggested changes in a PR not rendering the original line [2];
- bug trackers not showing more than the 40th page [3].
Might seem nitpicky but it was just over the last week... I have a whole bunch of other bugs on my mind, and unfortunately, it's only gotten worse over the years. To the point where I almost don't care anymore.
[1] https://github.com/PokeAPI/sprites/pull/284#issuecomment-585...
[2] https://github.com/Delgan/loguru/pull/1516#discussion_r41268...
If GH.com is anything like GHE, the number of moving parts is staggering.
Seeing as they have infinity tokens to spend on godlike secret AI, isn't it weird that those same bugs are still sitting on the bugtracker? Shouldn't Microsoft just pull up the secret OpenAI panel and prompt "fix all github bugs, triage out primitive public-level AI slop first"?
1. Microsoft/OpenAI have their incredible world destroying AI surely this should be a non-issue as coding is solved.
2. Are their customers the only ones using AI while gitlab/{competitor} customers are untouched by AI?
"Change default base repository for pull requests on forks" - https://github.com/orgs/community/discussions/11729
This has always been the case to a certain extent, but the effect has now been amplified to the point that certain complex bugs will likely remain unfixed forever if AI can't fix them easily.
Github seems to get slower and slower, while Forgejo running on my $5 VPS lets me fly through repos and files instantly.
I also get docker registry hosting.
Maybe that was the point, if its not front and center then nobody will use the social features.
Regardless, I think its hard to balance UI for normies and UI for techies, I think theres also a lot of brogrammers who might think they like being techies but their version of tech is lots of padding, whitespace, diffused colouring and not information density and consistency.
Personally, I have a negative almost visceral reaction when my tools change, because I learn my tools intimately and create expectations of where things will be- but this is also why I avoid tools which don’t have consistency in their UI too.
I get design/product people sometime that get all caught up in "we need to simplify" or there's not enough whitespace. Every time, the design/product person is not a user of the product, and the result is you ship their improvements, get blistering angry feedback (last time I even got the most prolific user and recommeder of our product calling me on my cell at 11pm) and revert.
> their version of tech is lots of padding, whitespace, diffused colouring and not information density and consistency
Exactly this. I think is speaks more to how frequently the designer uses the product versus actual users, and they don't understand the difference between UX for casual/infrequent users and people who spend all day in the product.
I’m not at all. People around here love to hate GitHub, and think any change to a product or design is incredibly regressive. These to combine and people lose their minds.
It shouldn't be. The dashboard literally doesn't work. There are features on the dashboard that literally do not work. There are features on the dashboard that lie to you. You cannot trust the dashboard.
It's also not necessarily useful because, while it might put my stuff in front, it's not the stuff I care about. And I don't care about all my stuff all the time. Why should I care about a pull request that I have open on a random repo from January? Why should that be one of the top items that I need to address?
More importantly, why can't I resolve it from here?
Why does the copilot chat not work? It doesn't. You type something in, you hit Enter. It takes you to another page. You leave that page, you go back to the dashboard. The dashboard doesn't work because it's blank, and the copilot chat never got sent. And you lost your prompt. GitHub lost my content. I put content into GitHub, and that content is no longer in GitHub. That is user-destructive behavior. It's horrible.
Let me be clear: I put data into GitHub. I hit submit. It took me to another page, and that data went missing. It's just chat, but it's still chat. It's still something I entered. I hit submit, and it's gone. That's from this new dashboard. That alone should be negativity enough.
I'm not asking GitHub to create me the perfect dashboard. What I am saying is that the dashboard that they provided is fairly useless. So useless that, of the entire dashboard, there are only two small little links in the middle of the top repositories that are remotely useful, and there's no way for me to sit there and manage all this stuff. Even if you filter stuff down, the filter options are so pathetically worthless that I don't know why they bothered. I'm not asking GitHub to create me the perfect dashboard. What I am saying is that the dashboard that they provided is fairly useless. So useless that of the entire dashboard, there's only two small little links in the middle of the top repositories that are remotely useful, and there's no way for me to sit there and manage all this stuff. Even if you filter stuff down, the filter options are so pathetically worthless that I don't know why they bothered.
If the goal of the dashboard was to make it easy for you to do your GitHub work, to get stuff done, then for me, they failed tremendously. I'm a developer. I've been a developer for many decades, and I like what I do. GitHub, for all its faults, has pieces that work really well, but the dashboard is absolutely not one of them. I feel like the dashboard is run by the same people who do the code review stuff, and they don't know what they're doing. They've done the dashboard. They've checked it off. They said, "Now you see your stuff front and center," and it's like, "Yay," but it's not stuff you care about.
So sure. We're not at the bottom of the trash anymore, but we're still in a pile of trash.
- only half the sidebar is being used, by the "top repositories" section
- i have my own agent and want copilot purged from view completely rather than being the first central item of the dashboard
- why is the changelog taking up 1/4 of the screen? move it to the navbar as a popover
- the content doesn't go full width so i'm losing a column or two worth of content
PRs and issues sections are the least worst parts of the dashboard and they're still worse than just using /notifications as a dashboard.
completely worthless.
It changed?
TIL
Except I discovered that it just doesn’t include things sometimes. Items that show up in the “this month” filter disappear in the “last 3 months” filter for example.
This is one of those things where if it only works 98% of the time, it’s next to useless. I can’t just pretend a few PRs each week don’t exist.
Central Question: What pragmatic work tracking advice do people have for tiny (1-4; 1 founder, 1-3 contractors) team sizes, analog or digital?
Context: I noticed a source of friction for my larger solo projects (1+ months) was a lack of structure and carrying the entire project in my head. Effective for hackathons but life is starting to force me into more context switching (getting older I guess). I've already refactored my work system to involve an analog weekly planner + weekly retro/plan ritual, heavier emphasis on digital calendar, adopting a two phase work philosophy (planning/grooming, task execution) often facilitated by pomodoro (5 minutes plan, 25 execute), and leaning on having a digital work tracking system.
I've taken a large bet on GitHub's ecosystem. Issues + "type:" labels let me create ticket types (spike, feature, bug) + "area:" labels (e.g. runtimes, category of concern (security, REST, client, ...), ...) allows me to gather and tag appropriate units of work. GitHub projects supports kanban boards and "filter by" or "slice by" features that are helpful. Pull Requests + Actions let me vet software additions. Issue/PR comment streams allow additional context capturing. Milestones & Releases let me plan larger epics and bundle my software. It's a robust digital system whose mental model makes sense in the context of delivering software.
I have an ambitious software project idea (multiplayer game software) that I'll eventually want to bring in a contractor or more. I want to stipulate some degree of interfacing with my system, even if it's just to capture the high level "this feature is handled by contractor A" and allow delegated delivery.
The points of friction so far have come from wrestling decision control with ai agents, and resisting the temptation to plan in too much detail too far into the future.
Given that brain dump, what advice might you have for me to help make for successful?
Does anyone use the dashboard?
I use git. Before that clearcase,p4,svn,cvs,even rcs... In all that time never did I need a web dashboard with clippy telling me what to focus on.
Emails were not good enough? Email is certainly more reliable than sh*thub.
I don't mean to be cynical, but the trend is very real, in my experience.
Or just skip all of this BS and let us design our own homepage with pre-defined components.
I ended up making a userscript to redirect github.com -> github.com/<user>/repos in the end :P
It told me he could not do that.
And I think "Why they put this useless button everywhere then?"
Please someone at github, hear this. Discussions are useless for feedback as you cannot subscribe to just the single thread you posted, only the entire discussion. That means I have a a binary choice of drinking the firehose or ignoring all future comments on some feedback I care about.
Please fix this.
https://github.com/orgs/community/discussions/208952#discuss...
Instead or alongside this, how about making notifications good? There's some concrete simple improvements that would help triaging in general.
1. Provide ways to filter notifications of a specific state (merged, shipped release, closed) so these can be handled in bulk easily
2. Filter by type (issue / pr / release)
3. Provide access to the done state as a filter and via the api, so we can use non github website tooling to manage the notifications
4. Filter by author (e.g. let me filter dependabot notifications so I can handle them in one pass)
5. Show and allow filters on PR check status so I can look at PRs that are ready for a quick next step rather than ones that require digging into failures etc.
6. Make this all available properly via the API so I can let my clanker interact with this stuff based on rules that it has to help me triage stuff. Right now there are enough missing fields from the notification APIs that it makes it impossible to work around the shortcomings of the notifications with tooling (without screen scraping /notifications).
All of these things would be better for interacting with work to be done.
A general rule on this is if the information would make it easier to understand what work is to be done, to choose it, to act on it in bulk or in batches of similar actions, then that info belongs in the UI and the API.
---
Also. Please make it possible to subscribe to a discussion comment, but unsubscribe from a discussion. I want to read replies to this comment, but don't care to get a notification on every reply to this entire discussion. Unsubscribing. Tag me if you want me to read a reply here.