-
Notifications
You must be signed in to change notification settings - Fork 519
Add document.GatherReleaseNotesDocument
and notes.GatherReleaseNotes
API
#1272
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
Conversation
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
/lgtm |
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.
/lgtm
Needs rebase. |
…es` API This simplifies the usage of the pkg/notes and pkg/document packages by introducting the two new API functions. The `CreateDocument` functions is now simply called `New` and takes the start and end rev as additional parameters. All tests and API consumers have been adapted as well. Signed-off-by: Sascha Grunert <[email protected]>
Rebased to resolve the conflict 🧛♂️ |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, justaugustus, saschagrunert 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 |
What type of PR is this?
/kind api-change
What this PR does / why we need it:
This simplifies the usage of the pkg/notes and pkg/document packages by
introducting the two new API functions. The
CreateDocument
functionsis now simply called
New
and takes the start and end rev as additionalparameters.
All tests and API consumers have been adapted as well.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?