Documenting json conflict files
Open
Nobody has claimed this yet.
- Dominant language
- Vue
- Stars
- 15
- Forks
- 22
- Avg merge
- 5d 11h
- Merged PRs (30d)
- 9
Description
It would be good to add a section on what happens when two users are trying to edit the same field of the same feature and mergin creates conf.json files.
Contributor guide
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
Review the existing documentation structure in the MerginMaps docs repository and investigate the documented behavior for two users editing the same field of the same feature. Add a section explaining how the conflict is handled and when mergin creates conf.json files; the work is done when this scenario and its outcome are clear to users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100