-
Notifications
You must be signed in to change notification settings - Fork 654
[Bug] Gitversion could not determine which branch to treat as the development branch #3091
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
Comments
We would need more information to resolve this. My hunch is that the checkout is a detached |
The checkout was on a branch. The clone was a deep clone using checkout@v2 actions with fetch-depth set to 0. |
Are you able to reproduce this in a public repository? |
I don't work much with public repository. The github repository contained Main and master branch but the default branch was master. I have now deleted the main branch and would test again. I would add more logs as I keep testing it. |
This one sort it out for us ( we are using azure repos / devops )
This prevents azure default checkout task from running a git shallow clone. Other option is to set this in the azure DevOps UI on the pipeline triggers (UNCHECK "Shallow fetch"). As @PaulFarry mentioned just above me :-) |
Worked for us! Thanks @pavelmateju |
This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. |
This issue was closed because it has been stalled for 30 days with no activity. Thank you for your contributions |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
Expected Behavior
SemVer
Actual Behavior
Unexpected error
Possible Fix
Steps to Reproduce
Context
Your Environment
Gitversion 5.10.1The text was updated successfully, but these errors were encountered: