Update teamcity docs with info about fetchallheads #1840
Merged
Conversation
This file contains hidden or 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
asbjornu
requested changes
Oct 5, 2019
Co-Authored-By: Asbjørn Ulsberg <[email protected]>
Co-Authored-By: Asbjørn Ulsberg <[email protected]>
|
@arturcic, do you have any ideas why the build is failing on AZDO? |
asbjornu
approved these changes
Oct 5, 2019
|
Fixed the build, you can merge @asbjornu |
|
Thanks for your contribution, @jakubsuchybio! 🙏 |
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.
Making PR for @asbjornu after requesting it in #1825
This PR adds more information for users using GitVersion with TeamCity in MainLine mode.
By default, TeamCity doesn't work with MainLine, because TeamCity only downloads current building branch and not the master, so gitversion can't figure out the version.
After this PR I think there should also be some changes to the code where the errors occurs. So that these errors are descriptive about this new documentation and users can fix this issue for them without any more hassle.
For more reference about this issue see:
#912, #1199, #1234, #1441, #1477 and #1825