Document #180
Merged
Document #180
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
|
/document |
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.
All Submissions:
Closes
Closes #166 properly
Types of changes
This change properly fixes 166 and should allow people to install directly from GitHub.
The workflow needs to be manually triggered on PRs with the /document comment. This will add any changes in documentation, as well as add any updates to RcppExport files.
An example of it in action can be seen here: buzacott#8
In future we can consider if we want this to happen automatically after the decision has been made to merge PRs. Otherwise we will have to remember to comment /document to keep the documentation up to date and to avoid breaking GitHub installs.
I think this PR should be merged, then we can run it on the HBV PR to get the proper files in the repo.