-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add "{status}" placeholder #23
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thank you. But let's add a safe-guard
Just realized an ambiguity -- this the status for the entire "build" (which could have multiple jobs/workflows). I am ok to merge as is, if you do not see a conflict/ambiguity to resolve while in this PR. |
@yarikoptic The statuses are for whatever's logs gets saved at the |
ah, gotcha... confirmed with looking at
in my config where I assumed it to be for a build I ended up with groupping of failed-vs-success for the same build in different directories. ok, let's proceed for now -- not yet sure if I really need the "build status" |
Closes #20.