AzureDevOpsDsc: Support publish wiki documentation#31
AzureDevOpsDsc: Support publish wiki documentation#31johlju merged 6 commits intodsccommunity:mainfrom
Conversation
|
@SphenicPaul small one to enable Wiki publish and also limit the property |
|
Integration tests cannot run until merged to main. |
There was a problem hiding this comment.
@johlju - Sorry for the delay in reviewing this - I've just the 1 comment relating to a grammatical error that looks to have existed before this change but might as well be fixed as part of this.
Reviewed 6 of 6 files at r1.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @johlju)
source/Classes/010.AzDevOpsProject.ps1, line 21 at r1 (raw file):
changed
This should probably be corrected to change (i.e. remove the d).
johlju
left a comment
There was a problem hiding this comment.
No worries. 🙂 We are all busy with day jobs. 🙂
Reviewable status: 5 of 6 files reviewed, 1 unresolved discussion (waiting on @SphenicPaul)
source/Classes/010.AzDevOpsProject.ps1, line 21 at r1 (raw file):
Previously, SphenicPaul (Paul J. Wilcox) wrote…
changedThis should probably be corrected to
change(i.e. remove thed).
Done.
SphenicPaul
left a comment
There was a problem hiding this comment.
Reviewed 1 of 1 files at r2.
Reviewable status:complete! all files reviewed, all discussions resolved
Pull Request (PR) description
wiki (issue #15).
This will publish the markdown documentation that is generated bu the
build pipeline.
WikiSource. Every markdown file in the folderWikiSourcewill be published to the GitHub repository wiki. The markdownfile
Home.mdwill be updated with the correct module version on eachpublish to gallery (including preview).
RequiredModules.ps1to latest pipeline pattern.build.yamlto latest pipeline pattern.SourceControlTypeto (for now)limit the parameter to the values
GitandTfvc.since that is now add automatically to the documentation (conceptual
help and wiki documentation).
This Pull Request (PR) fixes the following issues
Task list
file CHANGELOG.md. Entry should say what was changed and how that
affects users (if applicable), and reference the issue being resolved
(if applicable).
This change is