-
-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Close GitHub Discussions and merge it to GitHub Issues #1666
Comments
Done. |
😆 I was so confused. You can mark Q&A as answered, but otherwise yeah it's confusing to mark stuff as done. Makes sense to simplify but I did find it confusing as I thought discussions was better for "free form" discussion that didn't have a specific code related issue. Thanks for documenting your change though in here so I didn't keep wondering where it went. You do a great job of communicating changes 👍🏻 |
Discussion can be closed now. |
I changed the mind and reopened Discussions. |
I have opened GitHub Discussions, but I think we should close GitHub Discussions and merge it to GitHub Issues.
Task
The text was updated successfully, but these errors were encountered: