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

Show group detection conditions first #134

Merged
merged 1 commit into from
May 20, 2019

Conversation

jchesterpivotal
Copy link
Contributor

Currently, when outputting from group detection, the name of the buildpack is displayed ahead of the condition. For example:

  Buildpack-1: pass
  Buildpack-with-longer-name: pass
  BP-short: fail

As the example shows, conditions are not vertically aligned. This makes it harder to visually scan for 'pass', 'fail' etc. It also makes it harder to write scripts that automatically parse lifecycle output.

This commit puts the conditions ahead of the buildpack name:

  pass: Buildpack-1
  pass: Buildpack-with-longer-name
  fail: BP-short

(This PR replaces the pig's breakfast that I and git-duet created in #133)

Currently, when outputting from group detection, the name of the
buildpack is displayed ahead of the condition. For example:

  Buildpack-1: pass
  Buildpack-with-longer-name: pass
  BP-short: fail

As the example shows, conditions are not vertically aligned. This
makes it harder to visually scan for 'pass', 'fail' etc. It also
makes it harder to write scripts that automatically parse lifecycle
output.

This commit puts the conditions ahead of the buildpack name:

  pass: Buildpack-1
  pass: Buildpack-with-longer-name
  fail: BP-short

Signed-off-by: Jacques Chester <jchester@pivotal.io>
@jchesterpivotal
Copy link
Contributor Author

@jkutner @ekcasey FYI.

@jchesterpivotal
Copy link
Contributor Author

Are we awaiting a second approval?

@ekcasey ekcasey merged commit 1facd31 into buildpacks:master May 20, 2019
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.

4 participants