Allow user to define different cpmbits repositories
Open
- Dominant language
- Python
- Stars
- 11
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
Research direction
The issue body provides no files, tests, entry points, or acceptance criteria. Start by reading the repository structure and existing repository configuration, then clarify how users should define alternate cpmbits repositories and what behavior or tests would demonstrate completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cpp, python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100