LivelyKernel / LivelyKernel/lively4-server
detect conflicts when collaborating on files locally before github sync
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
idea: commit on every put and squash commits later as needed (either while syncing or when merging a feature branch).
Another option would be to keep a local edit history beside git... which would be easy to build but make everything just more complex.
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 names no files, tests, or entry points. Start by tracing how local file updates are stored and synchronized with GitHub, then clarify whether commits on every put or a separate local edit history is preferred. Done means detecting local collaboration conflicts before GitHub synchronization and defining how commits are later squashed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100