UCL-ARC / UCL-ARC/python-tooling
`git init` is mandatory
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 62
- Forks
- 10
- Avg merge
- 7d 6h
- Merged PRs (30d)
- 6
Description
Describe the Bug
Despite that we allow users to say "no" to the question about initialising a git repository, we have setuptools-scm in our pyproject.toml so one can't run
uv pip install -e .
if one hasn't initialised a repo. It might be simplest "just" to check that git is installed and error if not. But as-is, there's a bug in the questions vs. pyproject.toml.
To Reproduce
Cookiecut a project, say "no" to the git init question and see what things break 😄.
Expected Behaviour
No response
Actual Behaviour
No response
Version In Use
v1.0.1
Additional Context
- Cookiecutter version: 2.6.0
- Operating system: macOS
- Python version: 3.13
Though I'm pretty confident this isn't an OS/version-dependent problem.
Contributor guide
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 with the cookiecutter flow that asks whether to run git init, then inspect pyproject.toml and its setuptools-scm configuration. Reproduce the issue by creating a project, answering no, and running uv pip install -e .; done means the generated project handles that choice consistently without the reported installation failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100