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

Lifecycle Compatibility Verification #34

Merged
merged 1 commit into from
Jan 22, 2020

Conversation

jromero
Copy link
Member

@jromero jromero commented Dec 6, 2019

readable

Continuation of #29

Signed-off-by: Simon Jones <sijones@pivotal.io>
Signed-off-by: Javier Romero <jromero@pivotal.io>
@jromero
Copy link
Member Author

jromero commented Jan 7, 2020

@hone / @nebhale Any additional changes necessary for this to be approved?

@nebhale
Copy link
Contributor

nebhale commented Jan 9, 2020

I move for an FCP, ending 16 Jan, for merge. If @hone approves before that day, we'll merge early.

@hone
Copy link
Member

hone commented Jan 22, 2020

I do like how flags feel less hidden since it can be viewed in the help of a binary. There's pretty massive benefits to the env var too. Potentially, we could do both. This is a common pattern for many CLIs.

@ekcasey ekcasey merged commit f9eae34 into buildpacks:master Jan 22, 2020
@jromero jromero deleted the lifecycle-compat-verification branch January 27, 2020 22:22
nebhale added a commit that referenced this pull request Jan 29, 2020
[resolves #34]

Signed-off-by: Ben Hale <bhale@pivotal.io>
nebhale added a commit that referenced this pull request Jan 29, 2020
[resolves #34]

Signed-off-by: Ben Hale <bhale@pivotal.io>
nebhale added a commit that referenced this pull request Jan 29, 2020
[resolves #34]

Signed-off-by: Ben Hale <bhale@pivotal.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants