Set 'init.defaultBranch' in ci:setup to suppress 'git init' warning #172
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In Git 2.30+, the `git init` command outputs a warning if `init.defaultBranch` is not set in the Git configuration: git/git@675704c Setting this default in `ci:setup` ensures that the warning does not spam CI logs every time `git init` is run. This config change only affects new repos created by `git init`, not repositories cloned using `git clone`. Hatchet uses `git init` when the path passed to `App.new` is a local directory, and not a repository cloned via `hatchet.lock`. This changes the default branch for new repos from `master` to `main`, however this works without further changes, since Hatchet already uses `git push HEAD:main`, where `HEAD` will reference the current branch regardless of its choice of name. This change is also compatible with older versions of Git, since they ignore unknown config file entries. Fixes #165.
edmorley
force-pushed
the
edmorley/git-init-default-branch
branch
from
290ffda
to
db88a3a
Compare
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Git 2.30+, the
git initcommand outputs a warning ifinit.defaultBranchis not set in the Git configuration:git/git@675704c
Setting this default in
ci:setupensures that the warning does not spam CI logs every timegit initis run.This config change only affects new repos created by
git init, not repositories cloned usinggit clone. Hatchet usesgit initwhen the path passed toApp.newis a local directory, and not a repository cloned viahatchet.lock.This changes the default branch for new repos from
mastertomain, however this works without further changes, since Hatchet already usesgit push HEAD:main, whereHEADwill reference the current branch regardless of its choice of name.This change is also compatible with older versions of Git, since they ignore unknown config file entries.
Fixes #165.