Remove output folder from source #86
Merged
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
The `docs` folder contains the HTML version of the document. This folder should never be checked out (hence it should be in the `/gitignore` file). Though, we need it to be present while creating the documentation (hence it should be created in the `release` and in the `preview` targets in the `Makefile`). Also, the github release pipeline should create it (in the `docs` branch), hence the `--force` to the `git add` command in the release pipeline.
|
Approved in CoP meeting |
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.
The
docsfolder contains the HTML version of the document.This folder should never be checked out (hence it should be in the
/gitignorefile).Though, we need it to be present while creating the documentation (hence it should be created in the
releaseand in thepreviewtargets in theMakefile).Also, the github release pipeline should create it (in the
docsbranch), hence the--forceto thegit addcommand in the release pipeline.