Documenting json conflict files

Open
#171 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
json
Domain
documentation

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.

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.

Dominant language
Vue
Stars
15
Forks
22
Avg merge
5d 19h
Merged PRs (30d)
11

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MerginMaps/docs

All issues in MerginMaps/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.