xtriggers: documentation #3457
Merged
xtriggers: documentation #3457
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
oliver-sanders
force-pushed
the
xtrigger-docs
branch
from
7d0b75f to
59aada6
Compare
kinow
approved these changes
Nov 29, 2019
hjoliver
approved these changes
Dec 1, 2019
There was a problem hiding this comment.
Looks good; but not merging response to @kinow 's question. (Note we'll also need the "built-in" xtriggers documented in the User Guide - maybe they already are, I forget - along with how to do custom xtriggers via entry points).
oliver-sanders
force-pushed
the
xtrigger-docs
branch
from
59aada6 to
b350af7
Compare
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.
Provide Xtriggers with docstrings suitable for auto-documentation via Sphinx.
Part-addresses cylc/cylc-xtriggers#4
Requirements check-list
CONTRIBUTING.mdand added my name as a Code Contributor.