Use the cnabio fork of image-relocation #292
Merged
Conversation
This file contains 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
The original repository at github.com/pivotal/image-relocation has been archived and is not maintained. In order to keep that repo maintained, I have created a fork of it in our github organization and am updating us to use the new location. It is using a new go package name so that everyone down the dependency chain doesn't need to maintain a replace statement forever pointing to the new location. Signed-off-by: Carolyn Van Slyck <me@carolynvanslyck.com>
carolynvs
force-pushed
the
use-image-relocation-fork
branch
from
fc84351
to
4525e0a
Compare
vdice
approved these changes
Aug 15, 2022
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.
The original repository at github.com/pivotal/image-relocation has been archived and is not maintained. In order to keep that repo maintained, I have created a fork of it in our github organization and am updating us to use the new location.
It is using a new go package name so that everyone down the dependency chain doesn't need to maintain a replace statement forever pointing to the new location.