LivelyKernel / LivelyKernel/lively4-core

GH Sync Tool always clones master branch

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

Nobody has claimed this yet.

comp: sync tool effort1: easy (hours) P4: nice to have type: bug
Dominant language
JavaScript
Stars
89
Forks
25
PR merge metrics
No merged PRs in 30d

Description

Instead, we should check for the branch input field in the tool.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by locating the GH Sync Tool and its branch input field. Trace the cloning entry point to see where the branch is fixed to master. Done means cloning the branch selected in the input field rather than always cloning master.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.