Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Improve documentation around version strategies #4220

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

Merged
merged 10 commits into from
Oct 11, 2024
Merged

Improve documentation around version strategies #4220

merged 10 commits into from
Oct 11, 2024

Conversation

selfdocumentingcode
Copy link
Contributor

@selfdocumentingcode selfdocumentingcode commented Sep 21, 2024

Description

  • Improve listing of version strategies on "How it works" docs page
    • Update names to reflect recent code changes
    • Replace (incorrect) examples with a link to the main version strategies list
    • Concisely describe Mainline and TrackReleaseBranches version strategies
  • Improve listing of version strategies on "Configuration" docs page
    • Replace TrunkBased strategy listing with Mainline
  • Fix Edit Diagram link on "How it works" docs page
  • Update docs\readme.me build instructions to use correct target name for docs preview

Related Issue

#4219

Motivation and Context

I'm trying to understand how GitVersion works and the documentation makes it difficult at times.

How Has This Been Tested?

I built and ran a preview of /docs locally.

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@arturcic
Copy link
Member

  • Remove unused file docs\input\docs\references\mdsource\configuration.source.md

This one is actually used, and we have tests that check the content of the configuration.md based on the configuration.source.md. See #4104

@@ -25,8 +25,7 @@ public override void Setup(BuildContext context, ISetupContext info)
{ "BaseEditUrl", "https://github.com/gittools/GitVersion/tree/main/docs/input/" },
{ "SourceFiles", context.MakeAbsolute(Paths.Src) + "/**/{!bin,!obj,!packages,!*.Tests,!GitTools.*,}/**/*.cs" },
{ "Title", "GitVersion" },
{ "IncludeGlobalNamespace", false },
{ "IgnoreFolders", "**/mdsource" }
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be kept

@selfdocumentingcode
Copy link
Contributor Author

selfdocumentingcode commented Sep 23, 2024

I see. That feature is not mentioned anywhere in the readme file nor did any tests failed after removing it.

I will, of course, remove the change from the PR.
Thanks for pointing it out!

Edit: @arturcic I am right to assume that for this particular change I'm making to the configuration.md file, i.e. unrelated to the GitVersion workflows, I have to also make the same change in the configuration.source.md file in order for the change in configuration.md to not get reverted the next time the mkdocs.yml workflow runs?

@arturcic
Copy link
Member

I see. That feature is not mentioned anywhere in the readme file nor did any tests failed after removing it.

I will, of course, remove the change from the PR.
Thanks for pointing it out!

Edit: @arturcic I am right to assume that for this particular change I'm making to the configuration.md file, i.e. unrelated to the GitVersion workflows, I have to also make the same change in the configuration.source.md file in order for the change in configuration.md to not get reverted the next time the mkdocs.yml workflow runs?

Yes, please update the source file instead, as the configuration.md is updated from the source

@arturcic
Copy link
Member

arturcic commented Oct 1, 2024

@HHobeck can you check the changes for the documentations?

@HHobeck
Copy link
Contributor

HHobeck commented Oct 1, 2024

@HHobeck can you check the changes for the documentations?

Yes, I try to do the review tomorrow.

@HHobeck HHobeck self-requested a review October 8, 2024 12:42
Copy link
Contributor

@HHobeck HHobeck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May I ask you to document this? #4248

Updated the configuration documentation to specify that the order in which version strategies are specified does not matter.
@selfdocumentingcode
Copy link
Contributor Author

May I ask you to document this? #4248

Sure! Check my latest commits.

@arturcic arturcic added this to the 6.x milestone Oct 11, 2024
@arturcic
Copy link
Member

@HHobeck if there are no additional changes that need to be added, please merge this PR

@HHobeck HHobeck enabled auto-merge (rebase) October 11, 2024 17:36
@HHobeck
Copy link
Contributor

HHobeck commented Oct 11, 2024

@HHobeck if there are no additional changes that need to be added, please merge this PR

Not sure why just the auto merge option is shown

@arturcic arturcic disabled auto-merge October 11, 2024 19:35
@arturcic
Copy link
Member

I disabled auto-merge, but because there are some required actions (that are not run because only docs where changed) it's in pending state, so I will just merge

@arturcic arturcic merged commit baaab9a into GitTools:main Oct 11, 2024
6 checks passed
Copy link
Contributor

mergify bot commented Oct 11, 2024

Thank you @selfdocumentingcode for your contribution!

@arturcic arturcic modified the milestones: 6.x, 6.0.3 Oct 15, 2024
@gittools-bot
Copy link

🎉 This issue has been resolved in version 6.0.3 🎉
The release is available on:

Your GitReleaseManager bot 📦🚀

@arturcic arturcic linked an issue Oct 17, 2024 that may be closed by this pull request
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Docs]: Confusing/missing documentation around strategies
4 participants