harness pull only support the git clone;

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
git, go
Domain
cli, developer-experience

Research direction

Start by tracing the harness pull repo <repo_id> command and its git clone and authentication flow. Define whether id-less pull, separate clone and pull commands, or persistent git authentication is the intended behavior, then verify that subsequent git pull and possibly git push do not require manual PAT entry again.

Written by the indexing model from the issue text.

Description

Description:

harness pull repo <repo_id> , works for the git clone, but later if some one wants to update the repo through git pull, it requires manual authentication step again, we should support id-less harness pull repo or may be clone and pull separately so that we can support the git pull and also may be git push because otherwise it doesn't add any advantage for the user he has to again enter the pat-token for the git pull.

We can otherwise also support validating the git directly and then onwards user can use git, we can like setup things for the repo.

Dominant language
Go
Stars
22
Forks
10
Avg merge
14h 28m
Merged PRs (30d)
54

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.

More from harness/cli

All issues in harness/cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.