Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Evolving GitHub Issues

github.blog

Post reply on HN
Print view View original

11–20 of 92 posts

Re: Evolving GitHub Issues

#12

Post by jeremy_k »

ProxCoques wrote: post #7

If Issues could be restricted to repo maintainers (with everyone else using Discussions), it would make contributing to F/LOSS projects far easier because you could easily see what the team was "thinking" (PR lists aren't like that). As it is, most Issues are polluted by random support requests, suggestions and open-ended chat which obscures the focus so much that sometimes I just can't tell what they need help with,…

I agree. The issue with Issues and Discussions is no one knows where to put content. Most falls into Issues because Discussions aren't always enabled and Issues were the original dumping ground.

It would be nice to know that if you want to ask random questions or get guidance on how to use the project, go to Discussions. If you're looking for real bug reports, go to Issues. I'm not sure how to enforce Issues being only bug reports though. The first thing that comes to mind is having a triaging mechanism, but that puts more onus on maintainers to actually look through everything submitted and make a decision on it.

Re: Evolving GitHub Issues

#13

Post by schmichael »

poorman wrote: post #8

> Earlier this year, we introduced the private beta of increased project item limits, expanding the capacity from 1,200 to 50,000 items in a project. This reminds me why smaller companies can steal market share from larger companies. I can understand that at GitHub scale, it's probably difficult to support more that 1,200 items per project. The result? The entire ecosystem has these limits imposed on them. A smaller…

You misunderstand: the keyword in that quote is “project.”

GitHub projects are boards, not repositories. I don’t know if there’s a limit on the number of issues repositories can have (nomad is over 5k).

I’m not actually sure how valuable a board with over 1k items on it is in practice.

Re: Evolving GitHub Issues

#15

Post by cynicalpeace »

These are some nice updates.

However, it made me think of how much time and money is spent just on organizing things, even when organizing something doesn’t make things go better.

In fact, the best teams I’ve worked on have a bias against organizing and a “just do it now” mentality. It depends on the specific case of course. But as a culture, software engineers have a bias towards organizing too much as opposed to not enough.

Re: Evolving GitHub Issues

#16

Post by vinnymac »

yu3zhou4 wrote: post #10

I wish I could turn off Issues without archiving a repo

Maybe I am misunderstanding you somehow, but you can turn off Issues without archiving a repository, I have several like that. If I attempt to navigate to `/issues`, it redirects me to `/pulls`. And the Issues tab is not visible whatsoever.

Have you tried `/settings` -> Features -> [ ] Issues ?

Post reply on HN