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 now supports a way to create default community files for the entire org (PyCQA in this case). This is a great way to establish a common code-of-conduct if one is not set for one of the repos in PyCQA. And in some cases, a repo may want to just default to the org level as the code-of-conduct is updated with new versions. Other default files can be added as well, but I think the CoC provides the most value right now. Here is the GitHub documentation on such:
By the way, maybe this issue isn't strictly on the meta repo since in order to support default files, a new repo called ".github" would need to be created.
GitHub now supports a way to create default community files for the entire org (PyCQA in this case). This is a great way to establish a common code-of-conduct if one is not set for one of the repos in PyCQA. And in some cases, a repo may want to just default to the org level as the code-of-conduct is updated with new versions. Other default files can be added as well, but I think the CoC provides the most value right now. Here is the GitHub documentation on such:
https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file
The one problem I can foresee being an issue for PyCQA is that its current code-of-conduct is an RST file instead of markdown.
The text was updated successfully, but these errors were encountered: