-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add initial documentation for Runs #2943
Conversation
/kind documentation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding these @imjasonh ! Generally looks good, my 2 main asks:
- can we link to it from somewhere? e.g. from the docs/README and/or from the pipelines doc (we could put a placeholder in for where we'll add more on custom tasks)
- did we merge any PRs yet that actually make the Runs DO something? (i'm not sure) - if not, could we make it clear that the Run type doesn't yet do anything (in the situation where we do a release tomorrow for example, we'd want the docs to reflect the fact that the type exists but doesnt yet do anything - unless it does in which case ignore me!)
This is still incomplete as more fields and features will be added to the Run type. This doc should also probably explain the responsibilities of a custom task controller.
hey all! we just did a release with this functionality in it and no docs 😬 /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bobcatfish The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This is still incomplete as more fields and features will be added to
the Run type. This doc should also probably explain the responsibilities
of a custom task controller.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
/assign @bobcatfish