getting pull/push/fetch url

getting pull/push/fetch url

[clime]

[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]

Hello,

for my app, i need to be able get remote urls (fetch/pull/push) so
that i can derive some information from those, e.g. pull url netloc
from which i derive where other custom endpoints (binary file storage)
related to the remote git repo is located. This is just one example. I
am also using fetch url to store it into the composed package that i
generate by the app.

...And I also want to support git down to 1.7.1 (maybe i could live
with 1.8.3, not sure now)

Now, the problem is that getting those urls (fetch/pull/push) doesn't
seem to be an easy task. Currently i have the attached scripts to do
that. But i noticed that older gits like 1.7 use origin as a fallback
for pull url whereas the newer raise an error.

My question is if there is a better way to determine the urls that
would be backward compatible and easier than what i am doing right
now.

I could probably tweak my app to only use fetch url but then i won't
support triangle workflow so i would like to know if there is some
better option.

Thank you
clime

[-- Attachment #2: git_push_url --]
[-- Type: application/octet-stream, Size: 883 bytes --]

#!/bin/bash

# DESCRIPTION:
#
# Get branch push url.

function git_branch_push_remote {
    branch_push_remote="$(git -C "$GIT_ROOT" config --get branch."$GIT_BRANCH".pushRemote)"

    if [ -z "$branch_push_remote" ]; then
        branch_push_remote="$(git -C "$GIT_ROOT" config --get remote.pushDefault)"
    fi

    if [ -z "$branch_push_remote" ]; then
        branch_push_remote="$(git -C "$GIT_ROOT" config --get branch."$GIT_BRANCH".remote)"
    fi

    echo "$branch_push_remote"
}

function git_branch_push_url {
    branch_push_remote="$(git_branch_push_remote)"

    push_url="$(git -C "$GIT_ROOT" config --get remote."$branch_push_remote".pushurl)"
    if [ -z "$push_url" ]; then
        push_url="$(git -C "$GIT_ROOT" config --get remote."$branch_push_remote".url)"
    fi

    echo "$push_url"
}

url="$(git_branch_push_url)"

if [ -n "$url" ]; then
    echo "$url"
fi

[-- Attachment #3: git_pull_url --]
[-- Type: application/octet-stream, Size: 276 bytes --]

#!/bin/bash

# DESCRIPTION:
#
# Get branch pull url.

function git_branch_remote_url {
    git -C "$GIT_ROOT" config --get remote."$(git -C "$GIT_ROOT" config --get branch."$GIT_BRANCH".remote)".url
}

url="$(git_branch_remote_url)"

if [ -n "$url" ]; then
    echo "$url"
fi

[-- Attachment #4: git_fetch_url --]
[-- Type: application/octet-stream, Size: 399 bytes --]

#!/bin/bash

# DESCRIPTION:
#
# Get branch fetch url (with origin url as a fallback).

function git_branch_remote_url {
    git -C "$GIT_ROOT" config --get remote."$(git -C "$GIT_ROOT" config --get branch."$GIT_BRANCH".remote)".url
}

url="$(git_branch_remote_url)"

if [ -z "$url" ]; then
    url="$(git -C "$GIT_ROOT" config --get remote.origin.url)"
fi

if [ -n "$url" ]; then
    echo "$url"
fi

Re: getting pull/push/fetch url

[Eric Sunshine]

On Fri, May 17, 2019 at 3:30 AM clime <clime7@gmail.com> wrote:
> for my app, i need to be able get remote urls (fetch/pull/push) so
> that i can derive some information from those, e.g. pull url netloc
> from which i derive where other custom endpoints (binary file storage)
> related to the remote git repo is located. This is just one example. I
> am also using fetch url to store it into the composed package that i
> generate by the app.
>
> Now, the problem is that getting those urls (fetch/pull/push) doesn't
> seem to be an easy task. Currently i have the attached scripts to do
> that. But i noticed that older gits like 1.7 use origin as a fallback
> for pull url whereas the newer raise an error.
>
> My question is if there is a better way to determine the urls that
> would be backward compatible and easier than what i am doing right
> now.

Perhaps not a complete answer (and I'm sure people more familiar with
the topic can provide better direction), but have you tried querying
this information via higher-level commands rather than low-level
git-config? For instance, to get the name of the remote for a branch:

    git branch --list --format='%(upstream:remotename)' $BRANCH

and, to get the fetch URL for a remote:

    git remote get-url $REMOTE

or the push URL:

    git remote get-url --push $REMOTE

Re: getting pull/push/fetch url

[clime]

On Fri, 17 May 2019 at 10:10, Eric Sunshine <sunshine@sunshineco.com> wrote:
>
> On Fri, May 17, 2019 at 3:30 AM clime <clime7@gmail.com> wrote:
> > for my app, i need to be able get remote urls (fetch/pull/push) so
> > that i can derive some information from those, e.g. pull url netloc
> > from which i derive where other custom endpoints (binary file storage)
> > related to the remote git repo is located. This is just one example. I
> > am also using fetch url to store it into the composed package that i
> > generate by the app.
> >
> > Now, the problem is that getting those urls (fetch/pull/push) doesn't
> > seem to be an easy task. Currently i have the attached scripts to do
> > that. But i noticed that older gits like 1.7 use origin as a fallback
> > for pull url whereas the newer raise an error.
> >
> > My question is if there is a better way to determine the urls that
> > would be backward compatible and easier than what i am doing right
> > now.
>
> Perhaps not a complete answer (and I'm sure people more familiar with
> the topic can provide better direction), but have you tried querying
> this information via higher-level commands rather than low-level
> git-config? For instance, to get the name of the remote for a branch:
>
>     git branch --list --format='%(upstream:remotename)' $BRANCH
>
> and, to get the fetch URL for a remote:
>
>     git remote get-url $REMOTE
>
> or the push URL:
>
>     git remote get-url --push $REMOTE

Right, the problem is that both constructs `git branch --list
--format=<format> <branch>` and `git remote get-url <remote>`
works only under git v2 (not exactly sure about the minor version) but
they do not work under git 1.7.1 and git 1.8.3, it
seems.

Anyway, i figured i was too fuzzy in what kind of url i actually need.
I thought about it a bit more and figured that I probably this

function git_branch_remote {
    branch_remote="$(git -C "$GIT_ROOT" config --get
branch."$GIT_BRANCH".pushRemote)"

    if [ -z "$branch_remote" ]; then
        branch_remote="$(git -C "$GIT_ROOT" config --get remote.pushDefault)"
    fi

    if [ -z "$branch_remote" ]; then
        branch_remote="$(git -C "$GIT_ROOT" config --get
branch."$GIT_BRANCH".remote)"
    fi

    if [ -z "$branch_remote" ]; then
        branch_remote="origin"
    fi

    echo "$branch_remote"
}

Because basically, if some wants to go for triangle workflow, then
push url remote should be preferred because
that's where user has write access. If not, then there is a fallback
to branch.<branch>.remote and to origin
eventually, which is just nice to have cause it makes a minimal setup
for my app easier.

So basically, it is possible that an effective (where git actually
pushes when `git push` is invoked) remote
for pushing will be different than what that function returns (e.g.
when git 1.7.1. is used which doesn't
know about branch.<branch>.pushRemote and remote.pushDefault) but it
doesn't really matter as long
as a user is able to make a local configuration where effective push
remote and remote returned by
the fuction will align.

Then i also need 'origin' being returned immediatelly after clean
clone but that's the case as well.

So when i have this kind of 'abstracted' remote, then i need to take
pushUrl on one place and fetch
url on another but there should be no problem there.

Sorry, i didn't realize i actually kind of this 'hybrid remote' thing.
There still might an easier way to write
that function (in a compatible way). Not sure about that.

Anyway, thanks
clime

Re: getting pull/push/fetch url

[clime]

On Fri, 17 May 2019 at 13:02, clime <clime7@gmail.com> wrote:
>
> On Fri, 17 May 2019 at 10:10, Eric Sunshine <sunshine@sunshineco.com> wrote:
> >
> > On Fri, May 17, 2019 at 3:30 AM clime <clime7@gmail.com> wrote:
> > > for my app, i need to be able get remote urls (fetch/pull/push) so
> > > that i can derive some information from those, e.g. pull url netloc
> > > from which i derive where other custom endpoints (binary file storage)
> > > related to the remote git repo is located. This is just one example. I
> > > am also using fetch url to store it into the composed package that i
> > > generate by the app.
> > >
> > > Now, the problem is that getting those urls (fetch/pull/push) doesn't
> > > seem to be an easy task. Currently i have the attached scripts to do
> > > that. But i noticed that older gits like 1.7 use origin as a fallback
> > > for pull url whereas the newer raise an error.
> > >
> > > My question is if there is a better way to determine the urls that
> > > would be backward compatible and easier than what i am doing right
> > > now.
> >
> > Perhaps not a complete answer (and I'm sure people more familiar with
> > the topic can provide better direction), but have you tried querying
> > this information via higher-level commands rather than low-level
> > git-config? For instance, to get the name of the remote for a branch:
> >
> >     git branch --list --format='%(upstream:remotename)' $BRANCH
> >
> > and, to get the fetch URL for a remote:
> >
> >     git remote get-url $REMOTE
> >
> > or the push URL:
> >
> >     git remote get-url --push $REMOTE
>
> Right, the problem is that both constructs `git branch --list
> --format=<format> <branch>` and `git remote get-url <remote>`
> works only under git v2 (not exactly sure about the minor version) but
> they do not work under git 1.7.1 and git 1.8.3, it
> seems.
>
> Anyway, i figured i was too fuzzy in what kind of url i actually need.
> I thought about it a bit more and figured that I probably this
>
> function git_branch_remote {
>     branch_remote="$(git -C "$GIT_ROOT" config --get
> branch."$GIT_BRANCH".pushRemote)"
>
>     if [ -z "$branch_remote" ]; then
>         branch_remote="$(git -C "$GIT_ROOT" config --get remote.pushDefault)"
>     fi
>
>     if [ -z "$branch_remote" ]; then
>         branch_remote="$(git -C "$GIT_ROOT" config --get
> branch."$GIT_BRANCH".remote)"
>     fi
>
>     if [ -z "$branch_remote" ]; then
>         branch_remote="origin"
>     fi
>
>     echo "$branch_remote"
> }
>
> Because basically, if some wants to go for triangle workflow, then
> push url remote should be preferred because
> that's where user has write access. If not, then there is a fallback
> to branch.<branch>.remote and to origin
> eventually, which is just nice to have cause it makes a minimal setup
> for my app easier.
>
> So basically, it is possible that an effective (where git actually
> pushes when `git push` is invoked) remote
> for pushing will be different than what that function returns (e.g.
> when git 1.7.1. is used which doesn't
> know about branch.<branch>.pushRemote and remote.pushDefault) but it
> doesn't really matter as long
> as a user is able to make a local configuration where effective push
> remote and remote returned by
> the fuction will align.
>
> Then i also need 'origin' being returned immediatelly after clean
> clone but that's the case as well.
>
> So when i have this kind of 'abstracted' remote, then i need to take
> pushUrl on one place and fetch
> url on another but there should be no problem there.
>
> Sorry, i didn't realize i actually kind of this 'hybrid remote' thing.
> There still might an easier way to write
> that function (in a compatible way). Not sure about that.
>
> Anyway, thanks
> clime

And sry for my previous email being a mess. I rushed too much
to write it.