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

Force checkout of k8s #37

Merged
merged 1 commit into from
Jun 26, 2021

Conversation

johnSchnake
Copy link
Contributor

To avoid re-cloning all of k8s I usually copy over
my repo from my normal path. But when I do that and am
on master I get warnings when trying to checkout the
given sha.

Since this is a kubernetes folder just for this project,
it seems reasonable to me to add the -f checkout and
discard local changes if they exist.

Signed-off-by: John Schnake jschnake@vmware.com

To avoid re-cloning all of k8s I usually copy over
my repo from my normal path. But when I do that and am
on `master` I get warnings when trying to checkout the
given sha.

Since this is a kubernetes folder just for this project,
it seems reasonable to me to add the `-f` checkout and
discard local changes if they exist.

Signed-off-by: John Schnake <jschnake@vmware.com>
Copy link
Contributor

@sladyn98 sladyn98 left a comment

Choose a reason for hiding this comment

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

LGTM

@friedrichwilken friedrichwilken merged commit 578e96a into kubernetes-sigs:master Jun 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants