Discussion should be in GH Org#217
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #217 +/- ##
=======================================
Coverage 97.72% 97.72%
=======================================
Files 17 17
Lines 881 881
Branches 44 44
=======================================
Hits 861 861
Misses 12 12
Partials 8 8
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
The Google Group has been archived, GitHub Discussions are not enabled in this repo
Vizonex
left a comment
There was a problem hiding this comment.
Looks good Let's see what others have to say about this.
| - name: >- | ||
| [🎉 NEW 🎉] | ||
| 🤷💻🤦 GitHub Discussions | ||
| url: https://github.com/aio-libs/propcache/discussions |
There was a problem hiding this comment.
Project-specific discussions are in-repo. The org-global announcements would be in the org discussions. So this doesn't need to be changed in the form.
There was a problem hiding this comment.
Something else I read implied people should go to the Org wide Discussion area.
Though per-repo makes sense, I'll update
webknjaz
left a comment
There was a problem hiding this comment.
I think we shouldn't send people to the org-global discussions in general. Most things should be attached to repos.
What do these changes do?
The Google Group has been archived, GitHub Discussions are not enabled in this repo.
Just a few small docs updates I noticed when looking round the repo
Are there changes in behavior for the user?
N/A
Related issue number
N/A
Checklist