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

Clarify the root directory comment #12659

Merged
merged 1 commit into from
Feb 1, 2021
Merged

Conversation

spzala
Copy link
Member

@spzala spzala commented Feb 1, 2021

A contributor had an issue when ran script changing the directory
name after clone. This was discussed on the etcd slack channel.

A contributor had an issue when ran script changing the directory
name after clone. This was discussed on the etcd slack channel.
@spzala
Copy link
Member Author

spzala commented Feb 1, 2021

/cc @nate-double-u

@nate-double-u
Copy link
Contributor

Slack thread link: https://kubernetes.slack.com/archives/C3HD8ARJ5/p1611945997006900

@nate-double-u
Copy link
Contributor

A contributor had an issue when ran script changing the directory
name after clone.

Not only if the folder name is changed after cloning -- if you fork the repo and rename it, then clone that renamed fork, it'll run into the same problem. An admittedly infrequent event I think.

The problem is that the genproto.sh script has an expectation of the repo's root folder name.

@@ -1,7 +1,7 @@
#!/usr/bin/env bash
#
# Generate all etcd protobuf bindings.
# Run from repository root.
# Run from repository root directory named etcd.
Copy link
Contributor

Choose a reason for hiding this comment

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

/lgtm

@spzala spzala merged commit e897daa into etcd-io:master Feb 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants