🔄 Synced file(s) with nebari-dev/.github (#1588)

Co-authored-by: Tania Allard <[email protected]>
Co-authored-by: nebari-sensei <null>

.github/ISSUE_TEMPLATE/release-checklist.md

@@ -1,11 +1,10 @@
 ---
 name: Release Checklist
 about: For maintainers only.
-title: '[RELEASE] <version>'
+title: "[RELEASE] <version>"
 labels:
- - 'type: release 🏷'
-assignees: ''
-
+  - "type: release 🏷"
+assignees: ""
 ---
 
 # Release Checklist
@@ -16,14 +15,12 @@ Scheduled release date - <yyyy/mm/dd>
 
 Release captain responsible - <@gh_username>
 
-
 ## Starting point - a new release is out
 
-- [x] Create *this* issue to track and discuss the upcoming release.
+- [x] Create _this_ issue to track and discuss the upcoming release.
 - [ ] Use the previous release issue for any final release-specific discussions, then close.
   - This can be a good time to debrief and discuss improvements to the release process.
 
-
 ## Looking forward - planning
 
 - [ ] [Create milestone for next release](https://github.com/nebari-dev/nebari/milestones) (if it doesn't already exist) and link it back here.
@@ -32,7 +29,6 @@ Release captain responsible - <@gh_username>
   - This will be, in large part, determined by the roadmap.
   - Is there a focus for this release (i.e. UX/UI, stabilization, etc.)?
 
-
 ## Pre-release process
 
 - [ ] Decide on a date for the release.
@@ -57,10 +53,10 @@ Release captain responsible - <@gh_username>
       - (Repeat steps if necessary)
   - [ ] [Update `RELEASE.md` notes.](https://github.com/nebari-dev/nebari/blob/main/RELEASE.md)
 
-
 ## Cut the official release
 
-*These steps must be actioned in the order they appear in this checklist.*
+_These steps must be actioned in the order they appear in this checklist._
+
 - [ ] [Tag, build and push docker images](https://github.com/nebari-dev/nebari-docker-images/releases/new)
 - [ ] [Update and cut release for `nebari-dask` meta package on Conda-Forge.](https://github.com/conda-forge/nebari-dask-feedstock)
 - [ ] [Cut PyPI release via GHA release workflow.](https://github.com/nebari-dev/nebari/releases/new)

.github/ISSUE_TEMPLATE/testing-checklist.md

@@ -1,23 +1,23 @@
 ---
 name: Testing Checklist
 about: For maintainers only.
-title: 'Testing checklist for <version>'
+title: "Testing checklist for <version>"
 labels:
- - 'type: release 🏷'
-assignees: ''
-
+  - "type: release 🏷"
+assignees: ""
 ---
 
 # Testing Checklist
 
-*Use/modify this checklist to capture the platform's core services that need to be manually tested .*
+_Use/modify this checklist to capture the platform's core services that need to be manually tested ._
 
 ## Manual testing: core services
 
 If the integration tests for all of the cloud providers are successful, that is a good sign!
 However, the following core services still need to be manually validated (until we can automate them).
 
 At minimum, the following services will need to be tested:
+
 - [ ] [Log into keycloak as root user](https://nebari-docs.netlify.app/how-tos/configuring-keycloak#change-keycloak-root-password)
   - [ ] [Add a user](https://nebari-docs.netlify.app/how-tos/configuring-keycloak#adding-a-nebari-user)
 - [ ] [Log into conda-store and create](https://nebari-docs.netlify.app/tutorials/creating-new-environments)

CODE_OF_CONDUCT.md

@@ -0,0 +1,8 @@
+# Nebari Code of Conduct
+
+Nebari is a community-oriented and community-led project.
+We value the participation of every member of our community and want to ensure that every contributor has an enjoyable and fulfilling experience.
+We are committed to creating a friendly and respectful place for learning, teaching, and contributing.
+Accordingly, everyone who participates in the Nebari project is expected to show respect and courtesy to other community members at all times.
+
+You can find the [Nebari Code of Conduct on the `nebari-dev/governance` repository](https://github.com/nebari-dev/governance/blob/main/CODE_OF_CONDUCT.md) and it applies to all spaces managed by Nebari including, but not limited to, in-person and online focus groups and workshops, and communications online via GitHub.