Issue #4715: Non-standard default branch: would deserve proper indication at the project home page - pagure

pagure

#4715 Non-standard default branch: would deserve proper indication at the project home page

Closed: Fixed Sep 16, 2020 by pingou. Opened Jan 21, 2020 by jpokorny.

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.

ttomecek commented Jun 16, 2020

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

Aug 7, 2020

Metadata Update from @ngompa:
- Issue set to the milestone: 5.12

Aug 7, 2020

pingou commented Aug 21, 2020

I'm wondering, where in the UI we should display this information.

Any idea?

Metadata Update from @pingou:
- Issue tagged with: easyfix

Aug 21, 2020

jlanda commented Aug 21, 2020

Next to the commit hash on the current state box?