You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Github has a feature called Discussions. From the github docs:
GitHub Discussions vs. GitHub Issues: When to use each
A common question among developers new to GitHub Discussions goes something like this: When should I use Discussions and when should I use Issues?
The short answer: Discussions are great for questions and ideas that require team communication to make a decision, while Issues are defined pieces of work.
The slightly longer answer: In any given project or sprint, you have things you need to discuss and those you need to do. Discussions are for—no surprise here—discussing things. Issues are for cataloguing the work you need to do after you’ve reached a decision about how to move forward.
I think using discussions will allow us to clean up the issue tracker, leaving there only real issues.
What do you think? Shall we enable "Discussions"?
The text was updated successfully, but these errors were encountered:
Github has a feature called Discussions. From the github docs:
I think using discussions will allow us to clean up the issue tracker, leaving there only real issues.
What do you think? Shall we enable "Discussions"?
The text was updated successfully, but these errors were encountered: