Template dev docs: Add page/section documenting that the rendered repo was made using this repo
Open
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
I don't think we have info linking back to this repo, how to run copier update, etc.?
Is a section in the dev docs enough, or should there also be a note in the README?
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 locating the dev docs and README mentioned in the issue, then review how the rendered repository currently relates to this template. Document that relationship and how to run copier update, resolving whether the guidance belongs only in dev docs or also in the README. Done when users can find and follow the update instructions.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100