Decide whether to import scope information from CarbonCopy
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 12
- Forks
- 2
- Avg merge
- 13d 3h
- Merged PRs (30d)
- 1
Description
This issue has no description.
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
The issue body names no files, tests, entry points, or acceptance criteria. Start by inspecting the repository structure and existing data-import paths, then determine what CarbonCopy scope information means and whether it belongs in this project. Done requires a documented decision and, if importing is chosen, an agreed implementation scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100