Consider renaming `site` to `cactus`
Open
Nobody has claimed this yet.
- Dominant language
- Reason
- Stars
- 66
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
- Much more unlikely to accidentally match an existing file with that name (given the domain of the tool)
- Makes it more obvious that something is related to the build tool
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
No files, tests, or entry points are named in the issue. Start by locating uses of site in the repository and determine whether the rename applies to the build tool, generated output, or both. Done means the intended references use cactus without breaking the static-site build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100