Skip to content
This repository was archived by the owner on Feb 24, 2021. It is now read-only.

Commit 6a5a86b

Browse files
authored
Merge pull request #342 from X-Guardian/patch-1
README.md: Move Publish Wiki Content section & Remove Legacy CHANGELOG Link from ToC
2 parents 1897361 + 87373a6 commit 6a5a86b

File tree

2 files changed

+35
-34
lines changed

2 files changed

+35
-34
lines changed

CHANGELOG.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,6 +74,8 @@
7474
- Added PowerShell Script Analyzer rules to check the following
7575
statements are in lower case: `if`,`foreach`,`do`,`while`,`for`,
7676
`try`,`catch`,`enum`,`class` ([issue #224](https://github.com/PowerShell/DscResource.Tests/issues/224)).
77+
- Moved `Publish Wiki Content` section in the `README.md` to the correct location.
78+
- Removed the legacy `CHANGELOG` link in the README.md table of contents.
7779

7880
## 0.3.0.0
7981

README.md

Lines changed: 33 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,6 @@ A full list of changes in each version can be found in the [change log](CHANGELO
6363
- [Deploy](#deploy)
6464
- [Publish examples to PowerShell Gallery](#publish-examples-to-powershell-gallery)
6565
- [Publish Wiki Content](#publish-wiki-content)
66-
- [Change Log](#change-log)
6766

6867
<!-- /TOC -->
6968

@@ -805,39 +804,6 @@ environment:
805804
* text eol=crlf
806805
```
807806

808-
### Publish Wiki Content
809-
810-
To opt-in to this task, change the appveyor.yml to include the opt-in task
811-
*PublishWikiContent*, e.g. `Invoke-AppVeyorDeployTask -OptIn PublishWikiContent`.
812-
813-
By opting-in to the *PublishWikiContent* task, the test framework will publish the
814-
contents of a DSC Resource Module Wiki Content artifact to the relevant GitHub Wiki
815-
repository, but only if it is a 'master' branch build (`$env:APPVEYOR_REPO_BRANCH -eq 'master'`).
816-
A Wiki Sidebar file will be generated, containing links to all of the markdown
817-
files in the Wiki, as well as as a Wiki Footer file. Any files contained within the
818-
`WikiSource` directory of the repository will also be published to the Wiki
819-
overriding any auto generated files.
820-
821-
> **Note:** It is possible to override the deploy branch in appveyor.yml,
822-
> e.g. `Invoke-AppVeyorDeployTask -Branch @('dev','my-working-branch')`.
823-
824-
#### Requirements/dependencies for publishing Wiki Content
825-
826-
- Publish only on 'master' build.
827-
- The `Invoke-AppveyorAfterTestTask` function must be present in the Appveyor
828-
configuration with a Type of 'Wiki' to generate the Wiki artifact.
829-
- A GitHub Personal Access Token with `repo/public_repo` permissions for a user
830-
that has at least `Collaborator` access to the relevant DSC Module GitHub repository
831-
must be generated and then added as a
832-
[secure variable](https://www.appveyor.com/docs/build-configuration/#secure-variables)
833-
called `github_access_token` to the `environment` section of the repository's
834-
`appveyor.yml` file.
835-
- The GitHub Wiki needs to be initialized on a repository before this function is run.
836-
837-
> **Note:** Currently Wiki content files are only added or updated by the function,
838-
> not deleted. Any deletions must be done manually by cloning the Wiki repository and
839-
> deleting the required content.
840-
841807
#### Contributor responsibilities
842808

843809
Contributors that add or change an example to be published must make sure that
@@ -897,3 +863,36 @@ Contributors that add or change an example to be published must make sure that
897863
Defaults to 'Just some sample text to write to the file'.
898864
#>
899865
```
866+
867+
### Publish Wiki Content
868+
869+
To opt-in to this task, change the appveyor.yml to include the opt-in task
870+
*PublishWikiContent*, e.g. `Invoke-AppVeyorDeployTask -OptIn PublishWikiContent`.
871+
872+
By opting-in to the *PublishWikiContent* task, the test framework will publish the
873+
contents of a DSC Resource Module Wiki Content artifact to the relevant GitHub Wiki
874+
repository, but only if it is a 'master' branch build (`$env:APPVEYOR_REPO_BRANCH -eq 'master'`).
875+
A Wiki Sidebar file will be generated, containing links to all of the markdown
876+
files in the Wiki, as well as as a Wiki Footer file. Any files contained within the
877+
`WikiSource` directory of the repository will also be published to the Wiki
878+
overriding any auto generated files.
879+
880+
> **Note:** It is possible to override the deploy branch in appveyor.yml,
881+
> e.g. `Invoke-AppVeyorDeployTask -Branch @('dev','my-working-branch')`.
882+
883+
#### Requirements/dependencies for publishing Wiki Content
884+
885+
- Publish only on 'master' build.
886+
- The `Invoke-AppveyorAfterTestTask` function must be present in the Appveyor
887+
configuration with a Type of 'Wiki' to generate the Wiki artifact.
888+
- A GitHub Personal Access Token with `repo/public_repo` permissions for a user
889+
that has at least `Collaborator` access to the relevant DSC Module GitHub repository
890+
must be generated and then added as a
891+
[secure variable](https://www.appveyor.com/docs/build-configuration/#secure-variables)
892+
called `github_access_token` to the `environment` section of the repository's
893+
`appveyor.yml` file.
894+
- The GitHub Wiki needs to be initialized on a repository before this function is run.
895+
896+
> **Note:** Currently Wiki content files are only added or updated by the function,
897+
> not deleted. Any deletions must be done manually by cloning the Wiki repository and
898+
> deleting the required content.

0 commit comments

Comments
 (0)