django-commons / django-commons/controls
Add global defaults to the django-commons GitHub org
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- Avg merge
- 18m
- Merged PRs (30d)
- 1
Description
GitHub's .github repo acts as default storage for various things you'd usually put in your repo root or .github folder.
Thinks like:
- issues templates https://github.com/django-commons/.github/issues/2#issuecomment-4273402395
- security policy https://github.com/django-commons/.github/issues/3
- CoC https://github.com/django-commons/.github/issues/4
- funding links
Every repo can override those defaults by providing their own files. But it really helps to provide consistent workflows (via templates) as well as compliance (via CoC and security policies).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the django-commons/.github repository and the linked issues for issue templates, the security policy, the Code of Conduct, and funding links. Add the agreed global default files there, then verify that repositories without overrides receive those defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100