docs: for pull #348, fixed 1 outdated doc(s) #349
Conversation
This file contains hidden or 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
This comment has been minimized.
This comment has been minimized.
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.
✨ Autofixed 1 outdated doc(s)
This pull was automatically generated by Joggr to fix 1 outdated doc(s) due to code changes in pull #348
Fixed docs
The following docs were fixed:
docs/api/notification.md: The recent webhook code changes add a new validation: if a Contact's SubjectRef APIGroup is 'resourcemanager.miloapis.com', the resource's namespace must match that Contact's namespace, and unsupported API groups are now rejected. This requirement was not mentioned in the documented API spec, so the relevant descriptions and constraints have been added.How to fix
To fix the docs, you can either:
Powered by Joggr - The documentation assistant for your codebase.