Learn more about these different git repos.
Other Git URLs
Follow up for #106: non-standard default branch should be indicated so that
user is not confused on clone (see Neal's comment https://pagure.io/pagure/issue/4038#comment-545228)
it is apparent that it's indeed not master at hand
Just changed the default branch at GitHub mirror, have to conclude that they are always clear on which branch is meant.
Therefore, it'd likely be fair and more systemic to state the standard master branch visibly just as well if that's the case.
master
We've just hit this in git.centos.org where a repo only had a single branch which was not master (and we didn't touch the default branch setting). @carlgeorge tried to open a PR against such repo and got "Bad Request".
Would be nice if pagure was a little bit smarter when the default branch is not present - I would expect it to fall back to the first branch which exists in the repo, sorted at random.
Metadata Update from @ngompa: - Issue priority set to: High - Issue tagged with: bug
Metadata Update from @ngompa: - Issue set to the milestone: 5.12
I'm wondering, where in the UI we should display this information.
Any idea?
Metadata Update from @pingou: - Issue tagged with: easyfix
Next to the commit hash on the current state box? <img alt="branch.png" src="/pagure/issue/raw/files/ea50321133558ab5998a431b13a756a337d65ed6969e72251f4c97cd17a80e45-branch.png" />
Works for me.
:thumbsup: for me as well!
Thanks :)
Metadata Update from @pingou: - Issue assigned to pingou
Commit b7b0f1e fixes this issue
Login to comment on this ticket.