Repository navigation
Update repo config #1215
Description
- Default Tools
- pre-commit docs - done, Dev 861 pre commit #1212
- black
- flake8
- isort
- spellcheck
- pre-commit hook
- pytest with unit test - pending, IMPR: split unit/integration test #1211
- pre-commit docs - done, Dev 861 pre commit #1212
- Repo Security here
- auto version bump for some files(Github action yaml and later py dependencies) docs - after pre-commit and test/release actions
- scan vulnerability - already in placed, if there is any, will be shown here
- secret scan - done
- private vulnerability report docs - done
- code security scan/static code analysis docs - not enabled, we use flake
- Branch protection here
- no direct push to master branch, restrict admin push for datajoint-python - in placed
- PR checks - we want PR checks but we don’t want to block PR merge
- lint is required, config in branch protection
- checks same as pre-commit
- unit test - split to IMPR: split unit/integration test #1211
- Project management
- issue/pr labels: https://github.com/datajoint/datajoint-python/labels vs default labels - done
- auto triage label GHA doc, then it’s easier to filter issues that needs the first round review and then categorized by other labels - DEV-861-auto-label #1209
- we can link CONTRIBUTION.md - 'how to become a contributor'
- mention label, label issue/pr, link issues to pr, setup pre-commit
- github pr merge would auto close linked issue: https://github.com/orgs/community/discussions/23476, if needed create a sub issue instead
- Create a feature request or improvement request in datajoint-python, then possibly can be included in the datajoint-specs as standard
- Github Milestones/Project - needs discussion
- Github Project has different views that can used for roadmap or sprint: https://docs.github.com/en/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views
- need to split datajoint-python from this Project board that mixed with datajoint-elements DataJoint Open-Source Software, suggest to keep this board for datajoint-elements only, and create a different board for misc projects(doc, tutorial, etc.)
- mention label, label issue/pr, link issues to pr, setup pre-commit
- close stale issue bot - start with cleaning 1 year inactive issues docs Dev 861 stale issues #1208 , fix: 🐛 fix rate limit and rename #1214
- README.md badges blog
- Build status badges that tell you if the project is working as it should
- datajoint conda-forge badges
- citation badges
- Code coverage badges that show how much of the code is tested
- Version badges that show the latest version of the project
- License badges that tell you how the project can be used
- Compatibility badges that show what the project works with
- Build status badges that tell you if the project is working as it should
- Update issue template - DEV-861-auto-label #1209
- Github Discussion - done, https://github.com/datajoint/datajoint-python/discussions
- Citations
Activity