We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Splitting up updates into "task_updates" and "job_updates".
Job updates contain the previous state, and the current state (this change is the reason the event was emitted) (e.g. RUNNING->SUCCEEDED)
Task updates contain a list of task transitions (the reason for the event to be emitted) e.g. RUNNING->SUCCEEDED_NO_OP
The text was updated successfully, but these errors were encountered:
Essential as part of #59
Sorry, something went wrong.
Is this a ticket @ninjabear - the webhook is new in 0.3.0, so isn't this just part of the #59 commit?
In between this and the commit for #59 the code went through a linter, so it's going to be really hard to put this back there.
I think given that, this is the best way to represent the series of events that happened to the code-base
Okay, fair play
7a426a4
ninjabear
No branches or pull requests
Splitting up updates into "task_updates" and "job_updates".
Job updates contain the previous state, and the current state (this change is the reason the event was emitted) (e.g. RUNNING->SUCCEEDED)
Task updates contain a list of task transitions (the reason for the event to be emitted) e.g. RUNNING->SUCCEEDED_NO_OP
The text was updated successfully, but these errors were encountered: