pcdshub / pcdshub/shared-dotfiles
Configure git to automatically use pre-commit for all new cloned repositories
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3
- Forks
- 15
- Avg merge
- 7d 10h
- Merged PRs (30d)
- 1
Description
We discussed potentially setting up git such that pre-commit will always be used for new repositories where applicable.
Reference: https://pre-commit.com/#automatically-enabling-pre-commit-on-repositories
Reference: https://git-scm.com/docs/git-config#Documentation/git-config.txt-inittemplateDir
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
Read the linked pre-commit documentation and git-config init.templateDir documentation first. Then inspect the shared-dotfiles repository for existing shell or Git configuration entry points and determine how automatic setup should apply to new repositories. Done means the chosen configuration reliably enables pre-commit where applicable and can be verified with a newly cloned repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100