Skip to content

git remotes should be reordered upon init #8

@alexcabrera

Description

@alexcabrera

Having the upstream first causes things like this in GitX:

screen shot 2013-09-30 at 2 06 23 pm

Right now the .git/config file looks like this:

[core]
    repositoryformatversion = 0
    filemode = true
    bare = false
    logallrefupdates = true
    ignorecase = true
    precomposeunicode = false
[remote "upstream"]
    url = git@github.com:marquee/runtime.git
    fetch = +refs/heads/*:refs/remotes/upstream/*
[branch "master"]
    remote = upstream
    merge = refs/heads/master
[remote "origin"]
    url = git@git.droptype.com:tagtagtag-marquee-runtime.git
    fetch = +refs/heads/*:refs/remotes/origin/*
[remote "heroku"]
    url = git@heroku.com:tagtagtag-marquee-runtime.git
    fetch = +refs/heads/*:refs/remotes/heroku/*

We probably want it looking more like this (note order of remotes)

[core]
    repositoryformatversion = 0
    filemode = true
    bare = false
    logallrefupdates = true
    ignorecase = true
    precomposeunicode = false
[branch "master"]
    remote = upstream
    merge = refs/heads/master
[remote "origin"]
    url = git@git.droptype.com:tagtagtag-marquee-runtime.git
    fetch = +refs/heads/*:refs/remotes/origin/*
[remote "heroku"]
    url = git@heroku.com:tagtagtag-marquee-runtime.git
    fetch = +refs/heads/*:refs/remotes/heroku/*
[remote "upstream"]
    url = git@github.com:marquee/runtime.git
    fetch = +refs/heads/*:refs/remotes/upstream/*

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions