Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gitdot-cloned repo config lacks remote."origin".fetch #10

Open
smammy opened this issue Mar 21, 2025 · 0 comments
Open

gitdot-cloned repo config lacks remote."origin".fetch #10

smammy opened this issue Mar 21, 2025 · 0 comments

Comments

@smammy
Copy link
Contributor

smammy commented Mar 21, 2025

For reasons I haven't investigated, my ~/.dotfiles/config files are missing a fetch option for the "origin" remote. Here's the config for my clone of gitdot itself:

[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
[remote "origin"]
        url = https://github.com/smammy/gitdot.git
        fetch = +refs/heads/*:refs/remotes/origin/*
[branch "main"]
        remote = origin
        merge = refs/heads/main

And here's the same file for a dotfiles repo cloned by gitdot:

[core]
    repositoryformatversion = 0
    filemode = true
    bare = true
    excludesFile = .config/gitdot/exclude
[remote "origin"]
    url = https://github.com/smammy/dotfiles.git
[status]
    showUntrackedFiles = no
[branch "main"]
    remote = origin
    merge = refs/heads/main

The effect of this is that git doesn't create remote-tracking branches, so it can't show me anything in git branch -r and commits aren't labeled with remote refs in git log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant