LivelyKernel / LivelyKernel/lively.installer
if a merge conflict happens when updating a package...
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
the update process stops and the conflicted file is left with merge markers, possibly breaking the system.
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 or tests. Start by locating the package update process and reproduce an update with a merge conflict; trace how the conflicted file is handled. Done means the process has defined conflict behavior and does not leave merge markers that can break the system.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100