Repository navigation
Support campaign linking for projects already on disk with no remote. #192
Replies: 2 comments
|
When I first set up a campaign, most of my projects already lived on disk as local git repos that hadn't been pushed to a remote yet. Things like:
The friction was: to add these to a campaign with The ideal workflow would have been something like: camp project add --path ~/projects/my-internal-toolWhere camp links or references the existing local repo without requiring a submodule remote. This is especially useful for:
The campaign doesn't need to be portable in my case — it's a local orchestration layer for projects I'm actively developing on one machine. |
|
Thanks, David. This use case is now covered by Your example maps to: cd /path/to/campaign
camp project link ~/projects/my-internal-tool
# optional campaign-facing name:
camp project link ~/projects/my-internal-tool --name internal-toolIf you are already in the project directory, this also works: camp project link --campaign <campaign-name-or-id>The distinction is:
So this does not require a remote and is intentionally machine-local/non-portable. That matches the local orchestration case you described. On another machine, you would relink those projects there rather than expecting Appreciate the concrete examples here; they helped shape the split between |
Uh oh!
There was an error while loading. Please reload this page.
Setting up a campaign requires using camp project add with a url to a git remote, but a lot of people have projects on disc that haven't been pushed to a remote.
Local submodule resolution is fragile, but in cases where a campaign does not need to be portable it's possible to support submodules AND support linking projects stored elsewhere on the users disk.
Use this discussion to describe use cases where adding new submodules via git remote urls (like github, bitbucket, etc...) to repositories doesn't make sense, or adds unnecessary friction
All reactions