The-Strategy-Unit / The-Strategy-Unit/data_science
Advise on commit conventions
Open
Nobody has claimed this yet.
question
section: style guide
- Dominant language
- Jupyter Notebook
- Stars
- 11
- Forks
- 5
- Avg merge
- 5h 34m
- Merged PRs (30d)
- 1
Description
Decide what our advice is first, e.g. conventional commits, gitmoji and 'how to write a commit message' (thanks @StatsRhian for ideas/links).
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 comparing the three linked references: Conventional Commits, gitmoji, and “how to write a commit message.” The issue names no target file or documentation location, so first establish where the repository’s commit guidance belongs. Done means the team has chosen and documented a clear convention.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100