question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Feature request: command to add new repository

See original GitHub issue

Currently when using this tool one has to edit the config file and then run the vcspull command (maybe with filter on the new repo name) to get the new checkout.

I would propose to add some sort of command where you can do something like vcspull add <repoUrl> which will then generate an entry similar to:

<folder>:
  <repoName>: '<repoUrl>'

in the existing config. <folder> would be the folder from which the call is executed Obviously if the <folder> already exist it should just add an entry to that block. The <repoName> should be extractable from the <repoUrl>, if not it needs to be passed in the call.

Once this config update was done vcspull should be able to run its normal “checkout/update” logic on that new entry to create it.

That way you can add a new entry in the vcspull config and get the checkout right away.

Any thoughts on this?

Best regards Segaja

Issue Analytics

  • State:open
  • Created 2 years ago
  • Reactions:2
  • Comments:22 (16 by maintainers)

github_iconTop GitHub Comments

2reactions
aschleifercommented, Feb 25, 2022

@tony who knows, if you bring the current master codebase into the new structure (like moving the current “sync” code into its own file and proposing the structure and invocation) I might pick up the idea of this issue here and add the new command myself.

Working on the generator script in python got me enjoying python again, so if you don’t mind i could implement this “add” feature myself.

2reactions
tonycommented, Feb 24, 2022

That way we could have “sync” as the “normal sync”, maybe “import” or “scan” for your mentioned idea of scanning an existing folder structure and generating a config out of it. For the current example we could then do “add” for adding one new repo (as described in the description of this issue) and so on.

Noted

For code structure it could make sense to also split the code for these subcommands each into its own file. that way it is easier to maintain the code and “see” where what is happening.

Agreed

I like the idea of having a list of commands instead of starting with the principle that it will by default execute some magical command, and having that, I agree with you to add the vcspull sync

I agree with this sentiment. Next release will move the sync behavior to vcspull sync

Read more comments on GitHub >

github_iconTop Results From Across the Web

Request new feature in existing repository - knowledge-base
Click on the "New issue" button. Click on the Feature request "Get started" button. Create a new "Feature request". Click "Submit new issue"...
Read more >
Feature branch workflow - GitLab Docs
Clone project: git clone git@example.com:project-name.git ; Create branch with your feature: git checkout -b feature_name ; Write code. Commit changes: git commit ...
Read more >
Pull Requests | Atlassian Git Tutorial
The Feature Branch Workflow uses a shared Bitbucket repository for managing collaboration, and developers create features in isolated branches.
Read more >
How To Create a Pull Request on GitHub - DigitalOcean
With our file staged, we'll want to record the changes that we made to the repository with the git commit command. Commit Changes....
Read more >
Better code with Bitbucket: 4 starting steps
Step 1: Put your code in Bitbucket · Click + in the global sidebar on the left, and under Create new select Repository....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found