Merge branch 'main' into new-theme

Author: dikwickley

.deepsource.toml

@@ -1,2 +1,4 @@
 # lint codebase with black and ruff
 4e348d6b80c96da461fd866576c971b8a659ba15
+# migrate from black to ruff format
+22cea005629913208a85799372e045f353744add

.flake8

@@ -0,0 +1,4 @@
+node: $Format:%H$
+node-date: $Format:%cI$
+describe-name: $Format:%(describe:tags=true,match=*[0-9]*)$
+ref-names: $Format:%D$

.git-blame-ignore-revs

@@ -1,2 +1,3 @@
 *.py linguist-language=python
 *.ipynb linguist-documentation
+.git_archival.txt export-subst

.git_archival.txt

@@ -1,5 +1,5 @@
-name: 🐛 File a bug report
-description: X's behavior is deviating from its documented behavior.
+name: Bug Report
+description: Report incorrect behaviour in the library.
 labels: ["bug"]
 body:
   - type: markdown
@@ -27,7 +27,7 @@ body:
     attributes:
       label: Python Version
       description: Version of Python interpreter
-      placeholder: 3.9, 3.10, 3.11, etc.
+      placeholder: 3.10, 3.11, 3.12 etc.
     validations:
       required: true
   - type: input

.gitattributes

@@ -1,11 +1,11 @@
 blank_issues_enabled: true
 contact_links:
-  - name: ✨ Propose a new major feature
+  - name: Propose a new major feature
     url: https://github.com/zarr-developers/zarr-specs
     about: A new major feature should be discussed in the Zarr specifications repository.
-  - name: ❓ Discuss something on Zulip
+  - name: Discuss something on ZulipChat
     url: https://ossci.zulipchat.com/
-    about: For questions like "How do I do X with Zarr?", you can move to our Zulip Chat.
-  - name: ❓ Discuss something on GitHub Discussions
+    about: For questions like "How do I do X with Zarr?", consider posting your question to our developer chat.
+  - name: Discuss something on GitHub Discussions
     url: https://github.com/zarr-developers/zarr-python/discussions
     about: For questions like "How do I do X with Zarr?", you can move to GitHub Discussions.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,18 @@
+name: Documentation Improvement
+description: Report missing or wrong documentation. Alternatively, you can just open a pull request with the suggested change.
+title: "DOC: "
+labels: [documentation, help wanted]
+
+body:
+- type: textarea
+  attributes:
+    label: Describe the issue linked to the documentation
+    description: >
+      Please provide a description of what documentation you believe needs to be fixed/improved.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Suggested fix for documentation
+    description: >
+      Please explain the suggested fix and why it's better than the existing documentation.

.github/ISSUE_TEMPLATE/config.yml

@@ -3,7 +3,7 @@
 TODO:
 * [ ] Add unit tests and/or doctests in docstrings
 * [ ] Add docstrings and API docs for any new/modified user-facing classes and functions
-* [ ] New/modified features documented in docs/tutorial.rst
-* [ ] Changes documented in docs/release.rst
+* [ ] New/modified features documented in `docs/user-guide/*.rst`
+* [ ] Changes documented as a new file in `changes/`
 * [ ] GitHub Actions have all passed
 * [ ] Test coverage is 100% (Codecov passes)

.github/ISSUE_TEMPLATE/documentation.yml

@@ -1,15 +1,32 @@
 ---
 version: 2
 updates:
+  # Updates for main
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    groups:
+      actions:
+        patterns:
+          - "*"
+
+  # Updates for support/v2 branch
   - package-ecosystem: "pip"
     directory: "/"
+    target-branch: "support/v2"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     groups:
       requirements:
         patterns:
           - "*"
   - package-ecosystem: "github-actions"
     directory: "/"
+    target-branch: "support/v2"
     schedule:
       interval: "weekly"
+    groups:
+      actions:
+        patterns:
+          - "*"