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

Move to github.com/jetstack/cert-manager repo #145

Merged
merged 1 commit into from
Nov 3, 2017
Merged

Conversation

munnerz
Copy link
Member

@munnerz munnerz commented Oct 23, 2017

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Closes #134

Release note:

Move to 'jetstack' organisation. Action required: this will require updating your existing deployments to point to the new image repository, as new tags will not be pushed to the old 'jetstackexperimental/cert-manager-controller` repository.

/area admin
/assign
/release-note-action-required

@jetstack-bot jetstack-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. area/admin size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Oct 23, 2017
@munnerz
Copy link
Member Author

munnerz commented Oct 23, 2017

/release-note-action-required

@jetstack-bot
Copy link
Contributor

@munnerz: the /release-note and /release-note-action-required commands have been deprecated.
Please edit the release-note block in the PR body text to include the release note. If the release note requires additional action include the string action required in the release note. For example:

```release-note
Some release note with action required.
```

In response to this:

/release-note-action-required

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jetstack-bot jetstack-bot added release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action. and removed release-note Denotes a PR that will be considered when it comes time to generate release notes. labels Oct 23, 2017
@jetstack-bot
Copy link
Contributor

@munnerz PR needs rebase

@jetstack-bot jetstack-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 27, 2017
@jetstack-bot jetstack-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 3, 2017
@munnerz munnerz added the lgtm Indicates that a PR is ready to be merged. label Nov 3, 2017
@munnerz
Copy link
Member Author

munnerz commented Nov 3, 2017

/approve

@jetstack-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: munnerz

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@jetstack-bot jetstack-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 3, 2017
@jetstack-bot
Copy link
Contributor

Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions here.

@jetstack-bot jetstack-bot merged commit 2f159a0 into master Nov 3, 2017
@munnerz munnerz deleted the move-org branch November 3, 2017 18:26
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. lgtm Indicates that a PR is ready to be merged. release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Move to 'jetstack' organisation & quay.io image hosting
2 participants