<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=299844) </details> <!--IssueSummary end--> <!-- * Use this issue template for suggesting new docs or updates to existing docs. Note: Doc work as part of feature development is covered in the Feature Request template. * For issues related to features of the docs.gitlab.com site, see https://gitlab.com/gitlab-org/gitlab-docs/issues/ * For information about documentation content and process, see https://docs.gitlab.com/ee/development/documentation/ --> ### Problem to solve <!-- Include the following detail as necessary: * What product or feature(s) affected? * What docs or doc section affected? Include links or paths. * Is there a problem with a specific document, or a feature/process that's not addressed sufficiently in docs? * Any other ideas or requests? --> Since we support [Custom initial branch name](https://docs.gitlab.com/ee/user/project/repository/branches/#custom-initial-branch-name). We do not have instruction to push to a custom branch in [empty.html.haml](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/views/projects/empty.html.haml) ### Further details <!-- * Any concepts, procedures, reference info we could add to make it easier to use GitLab successfully? * Include use cases, benefits, and/or goals for this work. * If adding content: What audience is it intended for? (What roles and scenarios?) For ideas, see personas at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ or the persona labels at https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A --> Git client creates default branch as `master`. The customer has to change from `master` branch to the customer branch example `main` either by ``` git checkout -b main # creates the main branch from the command line, git client defaults to master ``` or by ``` git branch --move master main ``` ### Proposal <!-- Further specifics for how can we solve the problem. --> The proposal is to add another section to improve our instruction to help customers with custom branch push their code. Example. ``` %fieldset %h5= _('Push to a custom branch') %pre.bg-light :preserve cd existing_folder git init git remote add origin #{ content_tag(:span, default_url_to_repo, class: 'js-clone')} git add . git commit -m "Initial commit" git branch --move master #{ default_branch_name } - if @project.can_current_user_push_to_default_branch? %span>< git push -u origin #{ default_branch_name } ``` ### Who can address the issue <!-- What if any special expertise is required to resolve this issue? --> ### Other links/references <!-- E.g. related GitLab issues/MRs --> [Zendesk ticket](https://gitlab.zendesk.com/agent/tickets/189382) (internal only)