Set Default Branch in UI [168035627]

Assigned

Feature Request

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Sep 8, 2020 05:55PM

Please allow the ability to change the default branch for a source repository in the GCloud UI. The default branch is currently set to master. If this branch is not pushed to the repository, the message "No commits on the default branch" is displayed.

What you would like to accomplish:

Please add a control that allows the default branch to be changed from master to any existing branch. The default branch will be used to populate the UI on the homepage of a Cloud Source Repository.

How this might work:

This could work as a drop down selector populated by current branches in the repository. The UI element could be placed on the settings page for the repository.

If applicable, reasons why alternative solutions are not sufficient:

On 10/1/2020 Github will be setting the default branch of all newly created repositories to main instead of master. In addition, both Github, Azure and many other git hosting providers already allow changing the default branch.

https://github.com/github/renaming

Other information (workarounds you have tried, documentation consulted, etc):
Searched Cloud Source Repository documentation via

https://www.google.com/search?safe=off&q=site%3Acloud.google.com%2Fsource-repositories%2Fdocs+default+branch

Comments

br...@google.com <br...@google.com> #2Sep 9, 2020 03:15PM

Hi, could you please share screen shots of the UI you refer? Currently in the Cloud Source Repositories UI, in the top you will find:

YourRepository > Branch > file

You have a drop down in Repository and in Branch to change anytime.

Message last modified on Sep 9, 2020 03:16PM

csr.png

58 KB

View

Download

[Deleted User] <[Deleted User]> #3Sep 9, 2020 06:05PM

Hey! Thanks for taking a look at this. I have attached a screenshot of the home page of a Cloud Source Repository with the UI you mentioned open. You will see the main area says "No commits on the default branch." The default branch in this case is "main" (I am assuming that Cloud Source Repositories is expecting it to be "master"). As I mentioned in my original post, this is the naming system that github recommends and that they will be using by default starting 10/1/2020 (

https://github.com/github/renaming). I refer to github as an example because the repository in the screenshot is a mirror of a github repo, that has "main" as the default branch and no "master" branch.

Screen Shot 2020-09-09 at 1.58.59 PM.png

169 KB

View

Download

br...@google.com <br...@google.com> #4Sep 9, 2020 08:41PM

Hi, this feature request has been forwarded to the Source Repository product management team so that they may evaluate it. There is no timeline or implementation guarantee for feature requests. All communication regarding this feature request is to be done here.

de...@simpleclub.com <de...@simpleclub.com> #5May 12, 2021 10:14PM

Using master in now discourage by a Google guideline: https://opensource.google/docs/releasing/preparing/#inclusive

But not being able to switch away from master if one wants to properly use Cloud Source Repositories is working against this policy to strictly avoid it.

ke...@gmail.com <ke...@gmail.com> #6Aug 18, 2021 07:01PM

Shouldn't this issue has a higher priority as not being able to switch away from master is working against the inclusive policy?

bk...@coastsystems.net <bk...@coastsystems.net> #7Sep 10, 2022 08:07AM

Also waiting for this for a long time now. Thanks for making this product more useful and workable according to current practices.

Settings/General Settings/Select default branch.

Message last modified on Sep 10, 2022 08:09AM

lo...@cityblock.com <lo...@cityblock.com> #8Sep 26, 2022 08:49PM

Its extremely frustrating that this is still a bug at this point. all of our cloud functions broke in a Cloud Source Repositories <-> Github synced repo after the default branch was updated to main in github. The only workaround is to update hundreds of functions to pull their deps from a hardcoded alternate branch.

lu...@gmail.com <lu...@gmail.com> #9Oct 6, 2022 12:32PM

Is this still not fixed?

an...@foundation.com.au <an...@foundation.com.au> #10Oct 12, 2022 10:01PM

I just bumped into this as well. Renamed my master branch to trunk and pushed it, and was somewhat surprised to receive the UI that I did.

da...@gmail.com <da...@gmail.com> #11Dec 29, 2022 08:48PM

This is still not fixed? It's been default everywhere for 2 years now...

jg...@wemakeprice.com <jg...@wemakeprice.com> #12Jan 6, 2023 12:23PM

Is this still not fixed?

gh...@google.com <gh...@google.com> Jan 9, 2023 11:26AM

Assigned to gh...@google.com.

gh...@google.com <gh...@google.com> Jan 10, 2023 02:03PM

Reassigned to gc...@google.com.

fc...@adviso.ca <fc...@adviso.ca> #13Jan 12, 2023 03:42PM

Hi!
Same issue here!
I want the 'Main' branch as HEAD instead of using 'Master' to follow the new convention (like GitHub supports).

Almost 2 1/2 years since the issue creation it should already be fixed...

ja...@startupos.dev <ja...@startupos.dev> #14Jan 26, 2023 02:00PM

Any chance this gets fixed?

iv...@ivanlawrence.com <iv...@ivanlawrence.com> #15Feb 7, 2023 02:05AM

+1 hoping this gets solved sooner than later.

fe...@gmail.com <fe...@gmail.com> #16Mar 16, 2023 07:27PM

mi...@gmail.com <mi...@gmail.com> #17Mar 29, 2023 02:24AM

ha...@gmail.com <ha...@gmail.com> #18Apr 17, 2023 07:13PM

ba...@google.com <ba...@google.com> May 3, 2023 10:11AM

Reassigned to gh...@google.com.

gh...@google.com <gh...@google.com> May 4, 2023 09:14AM

Reassigned to gc...@google.com.

ai...@nihon-u.ac.jp <ai...@nihon-u.ac.jp> #19May 15, 2023 01:37AM

si...@gmail.com <si...@gmail.com> #20Aug 7, 2023 01:56AM

sh...@gmail.com <sh...@gmail.com> #21Aug 13, 2023 12:12AM

ma...@boardintelligence.com <ma...@boardintelligence.com> #22Sep 5, 2023 01:02PM

bk...@coastsystems.net <bk...@coastsystems.net> #23Sep 5, 2023 07:33PM

At this point I think they just want to push everyone off the non industry compliant service.

ju...@cube3.ai <ju...@cube3.ai> #24Oct 4, 2023 03:19PM

ye...@gmail.com <ye...@gmail.com> #25Oct 21, 2023 07:40AM

to...@3lll.asia <to...@3lll.asia> #26Nov 4, 2023 12:03PM

va...@gmail.com <va...@gmail.com> #27Nov 19, 2023 10:05PM

ma...@thoughtworks.com <ma...@thoughtworks.com> #28Jan 31, 2024 11:10AM

an...@simplexportal.com <an...@simplexportal.com> #29Feb 1, 2024 02:55PM

Still no way?

va...@sigscale.com <va...@sigscale.com> #30Mar 23, 2024 11:38AM

re...@gmail.com <re...@gmail.com> #31Mar 25, 2024 12:10AM

ma...@gmail.com <ma...@gmail.com> #32Apr 22, 2024 10:40AM

How is this coming along? I'm inclined to recommend my clients not to use Google Cloud Source Repositories until this is fixed, as they feel strongly about the related inclusivitivity issues.