(docs) Create basic documentation on how to set up CI providers #67
Conversation
This file contains 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
AdmiringWorm
force-pushed
the
ci-setup
branch
from
32adfed
to
26417b1
Compare
gep13
requested changes
Sep 9, 2020
|
|
||
| ## Using Azure Pipelines | ||
|
|
||
| There is currently no documentation on how to set up Cake Contrib addins for |
There was a problem hiding this comment.
I think that @pascalberger might be able to help here, as I know he runs some builds over there with Cake.Recipe.
There was a problem hiding this comment.
That was my thought as well, hence why I kept the header for Azure Pipelines 😆
There was a problem hiding this comment.
@gep13 @AdmiringWorm Yes, I can add something.
Co-authored-by: Gary Ewan Park <[email protected]>
|
@gep13 I added a new commit with the suggested changes 😄 |
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.
This pull request contains some documentation about how maintainers can set up builds on appveyor and/or GitHub actions by adding some workflow files as an example.
The available environment variables/secrets for each build provider is also being displayed to make it easier for maintainers to know what is available.
NOTE: The TOC was automatically generated by the vscode extension
Auto Markdwon TOC, and the markdown comments are related to that.