Merge branch 'datajoint:master' into master

Author: dimitri-yatsenko

.coveragerc

@@ -3,4 +3,4 @@ branch = False
 source = datajoint
 
 [report]
-show_missing = True
+show_missing = True

.devcontainer/devcontainer.json

@@ -28,7 +28,7 @@
 	// "runServices": [],
 	// Uncomment the next line if you want to keep your containers running after VS Code shuts down.
 	"shutdownAction": "stopCompose",
-	"onCreateCommand": "python3 -m pip install -q -e .[test]",
+	"onCreateCommand": "python3 -m pip install -q -e .[dev]",
 	"features": {
 		"ghcr.io/devcontainers/features/git:1": {},
 		"ghcr.io/devcontainers/features/docker-in-docker:2": {},
@@ -47,4 +47,4 @@
 	}
 	// Uncomment to connect as an existing user other than the container default. More info: https://aka.ms/dev-containers-non-root.
 	// "remoteUser": "devcontainer"
-}
+}

.devcontainer/docker-compose.yml

@@ -29,4 +29,3 @@ services:
 
     # Overrides default command so things don't shut down after the process ends.
     command: /bin/sh -c "while sleep 1000; do :; done"
-

.dockerignore

@@ -3,4 +3,4 @@ build
 *.egg-info
 dist
 .vscode
-__pycache__
+__pycache__

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,8 +1,8 @@
 ---
 name: Bug report
 about: Create a report to help us improve
-title: ''
-labels: 'bug'
+title: "Bug: "
+labels: ["bug", "triage"]
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,16 +1,16 @@
 ---
 name: Feature request
 about: Suggest an idea for a new feature
-title: ''
-labels: 'enhancement, awaiting-triage'
+title: "FEAT: "
+labels: ["enhancement", "triage"]
 assignees: ''
 
 ---
 
 ## Feature Request
 
 ### Problem
-A clear and concise description how this idea has manifested and the context. Elaborate on the need for this feature and/or what could be improved. Ex. I'm always frustrated when [...]
+A clear and concise description how this idea has manifested and the context. Elaborate on the need for this feature. Ex. I'm always frustrated when [...]
 
 ### Requirements
 A clear and concise description of the requirements to satisfy the new feature. Detail what you expect from a successful implementation of the feature. Ex. When using this feature, it should [...]

.github/ISSUE_TEMPLATE/improvement_request.md

@@ -0,0 +1,46 @@
+---
+name: Improvement request
+about: Suggest an idea for improvement
+title: "IMPR: "
+labels: ["enhancement", "triage"]
+assignees: ''
+
+---
+
+## Improvement Request
+
+### Problem
+A clear and concise description how this idea has manifested and the context. Elaborate on the need for what could be improved. Ex. I'm always frustrated when [...]
+
+### Requirements
+A clear and concise description of the requirements to satisfy the new improvement. Detail what you expect from a successful implementation of the improvement. Ex. When using this improvement, it should [...]
+
+### Justification
+Provide the key benefits in making this a supported improvement. Ex. Adding support for this improvement would ensure [...]
+
+### Alternative Considerations
+Do you currently have a work-around for this? Provide any alternative solutions or improvements you've considered.
+
+### Related Errors
+Add any errors as a direct result of not exposing this improvement.
+
+Please include steps to reproduce provided errors as follows:
+- OS (WIN | MACOS | Linux)
+- Python Version OR MATLAB Version
+- MySQL Version
+- MySQL Deployment Strategy (local-native | local-docker | remote)
+- DataJoint Version
+- Minimum number of steps to reliably reproduce the issue
+- Complete error stack as a result of evaluating the above steps
+
+### Screenshots
+If applicable, add screenshots to help explain your improvement.
+
+### Additional Research and Context
+Add any additional research or context that was conducted in creating this improvement request.
+
+For example:
+- Related GitHub issues and PR's either within this repository or in other relevant repositories.
+- Specific links to specific line or focus within source code.
+- Relevant summary of Maintainers development meetings, milestones, projects, etc.
+- Any additional supplemental web references or links that would further justify this improvement request.

.github/dependabot.yml

@@ -0,0 +1,12 @@
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "monthly"
+      day: "wednesday"
+      time: "9:00"
+      timezone: "America/Chicago"
+    groups:
+      all-actions:
+        patterns: [ "*" ]

.github/pr_labeler.yaml

@@ -0,0 +1,25 @@
+# https://github.com/actions/labeler
+breaking:
+- head-branch: ['breaking', 'BREAKING']
+bug:
+- head-branch: ['fix', 'FIX', 'bug', 'BUG']
+feature:
+- head-branch: ['feat', 'FEAT']
+documentation:
+- changed-files:
+  - any-glob-to-any-file:
+    - docs/**
+    - images/**
+    - README.md
+    - CHANGELOG.md
+    - CONTRIBUTING.md
+enhancement:
+- head-branch: ['enhance', 'improve', 'IMPR', 'DJEP']
+- changed-files:
+  - any-glob-to-any-file:
+    - '**'
+    - '!docs/**'
+    - '!images/**'
+    - '!README.md'
+    - '!CHANGELOG.md'
+    - '!CONTRIBUTING.md'

.github/release_drafter.yaml

@@ -0,0 +1,35 @@
+version-resolver:
+  major:
+    labels:
+      - 'breaking'
+  minor:
+    labels:
+      - 'feature'
+  patch:
+    labels:
+      - 'documentation'
+      - 'enhancement'
+      - 'bug'
+name-template: '$RESOLVED_VERSION'
+tag-template: 'v$RESOLVED_VERSION'
+categories:
+  - title: '💥 Breaking Changes'
+    labels:
+      - 'breaking'
+  - title: '🚀 Features'
+    labels:
+      - 'feature'
+  - title: '⚡️ Enhancements'
+    labels:
+      - 'enhancement'
+  - title: '🐛 Bug Fixes'
+    labels:
+      - 'bug'
+  - title: '📝 Documentation'
+    label: 'documentation'
+change-template: '- $TITLE(#$NUMBER)@$AUTHOR'
+change-title-escapes: '\<*_&' # You can add # and @ to disable mentions, and add ` to disable code blocks.
+template: |
+  $CHANGES
+
+  **Full Changelog**: https://github.com/$OWNER/$REPOSITORY/compare/$PREVIOUS_TAG...v$RESOLVED_VERSION