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

Suppress hint: Using 'master' as the name for the initial branch. This default branch name #427

Open
jsoref opened this issue Jan 17, 2021 · 2 comments · May be fixed by #465
Open

Suppress hint: Using 'master' as the name for the initial branch. This default branch name #427

jsoref opened this issue Jan 17, 2021 · 2 comments · May be fixed by #465

Comments

@jsoref
Copy link
Contributor

jsoref commented Jan 17, 2021

Downstream consumers of actions shouldn't see noise about that git itself is changing its default branch. When actions/checkout is used, it will be given a specific branch (or similar) to check things out...

Run actions/checkout@v2.0.0
  with:
    fetch-depth: 2
    repository: org/repo
    token: ***
    persist-credentials: true
    clean: true
    lfs: false
Syncing repository: org/repo
Working directory is '/home/runner/work/org/repo'
/usr/bin/git version
git version 2.30.0
Deleting the contents of '/home/runner/work/org/repo'
/usr/bin/git init /home/runner/work/org/repo
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint: 
hint: 	git config --global init.defaultBranch <name>
hint: 
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint: 
hint: 	git branch -m <name>
Initialized empty Git repository in /home/runner/work/org/repo/.git/
jsoref added a commit to jsoref/checkout that referenced this issue Mar 24, 2021
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
@jsoref jsoref linked a pull request Mar 24, 2021 that will close this issue
@snowshoes
Copy link

Git should not mess political correctness sht with open source world, you are correcting nothing but sht

jsoref added a commit to jsoref/checkout that referenced this issue Jun 7, 2023
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
jsoref added a commit to check-spelling/actions-checkout that referenced this issue Oct 18, 2024
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
jsoref added a commit to check-spelling/actions-checkout that referenced this issue Oct 18, 2024
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
jsoref added a commit to check-spelling/actions-checkout that referenced this issue Oct 18, 2024
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
@MestreLion
Copy link

@snowshoes this issue has nothing to do about "political correctness sht", but rather about suppressing a rather verbose 10-line useless warning, which can be easily done by actions/checkout by simply setting the hinted git config global setting to a dummy name

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

Successfully merging a pull request may close this issue.

4 participants
@MestreLion @jsoref @snowshoes and others