i must be missing something about remotes about legit HOT 5 CLOSED

The beauty of legit is that it's fully supplementary to the standard commands.

If you need to pull from another remote, than do so :)

from legit.

so in other words, i am not actually missing anything and legit is really designed to be used for single remote development -- i.e. it's meant for working more on my own stuff than collaborating with others.

sorry if i am being obtuse -- i am just trying to understand the big picture.

so if i want to use legit for a collaborative project like i outlined in my original comment above, and given that by default it works on the first remote, i should clone my fork first and then add the owner's repo as an additional remote and then when i want to fetch/pull from the owner's repo i do that with standard git commands. ya?

from legit.

Actually, someone just sent a pull request that allows you to do this:

$ git config legit.remote myfork

And it'll use that remote instead :)

It hasn't been released yet though.

from legit.

Has this change been merged?

I have two remotes:

(venv)~/git/whatever-proto1{master} $ git remote -v
heroku [email protected]:whatever-proto1.git (fetch)
heroku [email protected]:whatever-proto1.git (push)
origin [email protected]:whatever-proto1.git (fetch)
origin [email protected]:whatever-proto1.git (push)

legit publish

(venv)~/git/forever-proto1{master} $ legit publish

• master (published)
  sprint1 (published)
  sprint2 (published)
  sprint3 (published)
  sprint4 (published)
  sprint5 (published)
  test_sprint1 (unpublished)

Unfortunately, legit publish refuses to push to origin no matter what I've tried including:

git config legit.remote origin

and

git branch --set-upstream sprint1 origin/sprint1

As it stands, legit publish seems unusable with this configuration or am I missing some git command to tell legit which remote to use?

Thanks!

from legit.

This issue should have been fixed in recent versions of legit.

from legit.