Sorely needed. Tons of projects use issues for discussions/questions..or redirect to stackoverflow. I wonder what will be the reduction in stackoverflow due to this ? One request - have a global "discussions search" . Repos are interconnected to each other. I don't want to have to restrict my topic search to one repository's discussions
GitHub Discussions Beta
21–30 of 141 posts
Re: GitHub Discussions Beta
#22This seems like it'll be great for getting Q&A and random thoughts out of issues, but it won't replace broader boards and lists.
Re: GitHub Discussions Beta
#23GitHub is slowly eating the surrounding cities. Github pages replaced our hosted sites. Projects replaced Trello/Waffle and friends. Actions replaced Travis/CircleCI. Sponsors is about to hit Patreon, and now Discussions aims for a piece of StackOverflow pie... I think they are doing great in terms of performance and UI, it's hard to resist the convenience of having everything linked together in a coherent way. But t…
Why would it backfire? This centralized approach is the entire model for competitor Gitlab which has grown without issue so far.
Re: GitHub Discussions Beta
#24One problem with GitHub's version of these features is how they're tied to repos or organizations. My team works on many projects across repos and GitHub orgs and we have to use ZenHub instead of GitHub Projects because of these barriers. This seems like it'll be great for getting Q&A and random thoughts out of issues, but it won't replace broader boards and lists.
Re: GitHub Discussions Beta
#25Sorely needed. Tons of projects use issues for discussions/questions..or redirect to stackoverflow. I wonder what will be the reduction in stackoverflow due to this ? One request - have a global "discussions search" . Repos are interconnected to each other. I don't want to have to restrict my topic search to one repository's discussions
StackOverflow actively discourages "discussion"—it is for questions and answers. If anything, I'd say it overlaps more with issues than this.
Having a place to do this right next to the source code would be welcome (as long as there is global search as well)
E.g. https://kubernetes.io/docs/tasks/debug-application-cluster/t...
Stack Overflow
Someone else from the community may have already asked a similar question or may be able to help with your problem. The Kubernetes team will also monitor posts tagged Kubernetes. If there aren’t any existing questions that help, please ask a new one!
Re: GitHub Discussions Beta
#26Superb. Many open source projects still bounce you to Google Groups for discussion, which is archaic at this point. Even requires Google login just to read threads. Also it's often unclear what the policy is on raising questions in the issues tracker (smaller projects are usually fine with it, bigger projects get overwhelmed and don't want it). This will make it a much nicer separation for everyone and keep the issue…
Re: GitHub Discussions Beta
#27Re: GitHub Discussions Beta
#28Interesting. Will this be rolling out to other repositories at some point to beta-test?
Re: GitHub Discussions Beta
#29Earlier quoted context omitted.
StackOverflow actively discourages "discussion"—it is for questions and answers. If anything, I'd say it overlaps more with issues than this.
I don't know what stackoverflow discourages, but tons of projects explicitly mention "ask questions on stackoverflow with this hashtag" Having a place to do this right next to the source code would be welcome (as long as there is global search as well) E.g. https://kubernetes.io/docs/tasks/debug-application-cluster/t... Stack Overflow Someone else from the community may have already asked a similar question or may be…
In general, you aren't going to be able to discuss something on SO, and people aren't going to find answers in discussion boards because they don't make it easy to find those answers.
Re: GitHub Discussions Beta
#30Definitely a welcome addition, but it's funny that after all this time the solution was just to copy-paste the Issues tab and rename it. In fact in our public repos we have a "Discussion" label for such issues and it has worked pretty well.