Skip to content
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 support for patch-to-patch discovery mode #975

Merged
merged 1 commit into from
Dec 17, 2019
Merged

Add support for patch-to-patch discovery mode #975

merged 1 commit into from
Dec 17, 2019

Conversation

saschagrunert
Copy link
Member

@saschagrunert saschagrunert commented Dec 13, 2019

This adds the patch release discovery method to the release notes generator where it is now possible to generate the release notes by only setting the appropriate release branch:

> go run cmd/release-notes/main.go \
    --github-token <token> \
    --branch release-1.16
    --discover patch-to-patch

This results in an auto-discovery of the correct start and end SHAs:

INFO Parsing latest tag v1.16.4
INFO Parsing previous tag v1.16.3
INFO discovered start SHA b3cbbae08ec52a7fc73d334838e18d17e8512749
INFO discovered end SHA 224be7bdce5a9dd0c2fd0d46b83865648e2fe0ba

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Dec 13, 2019
@k8s-ci-robot k8s-ci-robot added area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release. labels Dec 13, 2019
@saschagrunert
Copy link
Member Author

/retest

@saschagrunert saschagrunert changed the title WIP: Add support for patch-to-patch discovery mode Add support for patch-to-patch discovery mode Dec 13, 2019
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 13, 2019
@saschagrunert saschagrunert changed the title Add support for patch-to-patch discovery mode WIP: Add support for patch-to-patch discovery mode Dec 13, 2019
@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 13, 2019
@saschagrunert saschagrunert changed the title WIP: Add support for patch-to-patch discovery mode Add support for patch-to-patch discovery mode Dec 13, 2019
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 13, 2019
This adds the patch release discovery method to the release notes
generator where it is now possible to generate the release notes by
only setting the appropriate release branch:

```
> go run cmd/release-notes/main.go \
    --github-token <token> \
    --branch release-1.16
    --discover patch-to-patch
```

This results in an auto-discovery of the correct start and end SHAs:

```
INFO Parsing latest tag v1.16.4
INFO Parsing previous tag v1.16.3
INFO discovered start SHA b3cbbae08ec52a7fc73d334838e18d17e8512749
INFO discovered end SHA 224be7bdce5a9dd0c2fd0d46b83865648e2fe0ba
```

Signed-off-by: Sascha Grunert <[email protected]>
@saschagrunert
Copy link
Member Author

Ready for review, PTAL

Copy link
Member

@cpanato cpanato left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice work on that amazing!
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 13, 2019
@justaugustus
Copy link
Member

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 17, 2019
@justaugustus
Copy link
Member

/retest

@k8s-ci-robot k8s-ci-robot merged commit 76b525a into kubernetes:master Dec 17, 2019
@k8s-ci-robot k8s-ci-robot added this to the v1.18 milestone Dec 17, 2019
@saschagrunert saschagrunert deleted the patch-to-patch branch December 17, 2019 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/release Categorizes an issue or PR as relevant to SIG Release. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants