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

git defaults to master - please include main in the default #2761

Open
snohio opened this issue May 9, 2022 · 0 comments
Open

git defaults to master - please include main in the default #2761

snohio opened this issue May 9, 2022 · 0 comments
Labels
Status: Good First Issue An issue ready for a new contributor. Triage: Confirmed Indicates and issue has been confirmed as described.

Comments

@snohio
Copy link

snohio commented May 9, 2022

Description

As a developer, I would like it when using the cookbook source git in cookbook 'chef-ingredient', git: 'https://github.com/chef-cookbooks/chef-ingredient.git', tag: 'v0.12.0' for example to check both the main and master branches (or switch to main) since that is now the git standard so that all of my new repos work as a source with my new repos

Chef Workstation Version

2022.4.861

Platform Version

Windows 10

Error:

Installing diiv >= 0.0.0 from git
Error: Failed to generate Policyfile.lock
Reason: (CookbookOmnifetch::GitCommandError) Git error: command `git rev-parse master` failed. If this error persists, try removing the cache directory at 'C:/Users/butler/AppData/Local/chef-workstation/cache/.cache/git/5ae8ed5064434cdaea0d4bda86b053bd9880fe35'.Output from the command:

fatal: ambiguous argument 'master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
@snohio snohio added the Status: Untriaged An issue that has yet to be triaged. label May 9, 2022
@vkarve-chef vkarve-chef added Triage: Confirmed Indicates and issue has been confirmed as described. Status: Good First Issue An issue ready for a new contributor. and removed Status: Untriaged An issue that has yet to be triaged. labels May 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Good First Issue An issue ready for a new contributor. Triage: Confirmed Indicates and issue has been confirmed as described.
Projects
None yet
Development

No branches or pull requests

2 participants