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.

Sign up for GitHub

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

Jump to bottom

Alternative to 'glide up' when modifying 'glide.yaml' #25

Open
Cryptophobia opened this issue Mar 21, 2018 · 1 comment
Open

Alternative to 'glide up' when modifying 'glide.yaml' #25

Cryptophobia opened this issue Mar 21, 2018 · 1 comment
Labels
upstream issue

Comments

@Cryptophobia
Copy link
Member

From @vdice on July 15, 2016 21:13

In deis/workflow-cli#128 we added logic around modifying a local glide.yaml with particular pkg/version values sent from the upstream controller-sdk-go PR job before building.

However, as noted in deis/workflow-cli#128 (comment), this may update other dependencies when we strictly only want the sdk dependency updated. Therefore, this ticket represents researching a better way to bring in a particular PR change in controller-sdk-go...

Copied from original issue: deis/workflow-cli#130
@Cryptophobia
Copy link
Member Author

From @vdice on July 18, 2016 15:15

It appears the ability to glide up <particular/pkg> is being tracked upstream/in glide by Masterminds/glide#252

@Cryptophobia Cryptophobia mentioned this issue Mar 21, 2018
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
upstream issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Cryptophobia