Think of branch-based workflow for managing different types of settings
Open
question
- Dominant language
- Haskell
- Stars
- 21
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
At the end of this issue I want to have clear view of how this should look like.
Contributor guide
Research direction
The issue names no files, tests, or entry points and only asks for a branch-based workflow for different settings. Start by reviewing the repository structure and existing synchronization workflow; the work is done when the proposed approach and its handling of settings types are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100