~ | | Initial addition of run-tool feature. This feature allows Status Updates
|
~ | | to have tools that are manually run, and allows Status Updates with a
|
| ~ | Allows Status Updates to have tools that are manually run, and allows
|
| ~ | Status Updates with a error/timeout state to be rerun. |
- | | error/timeout state to be rerun. |
| |
|
~ | | A new StatusUpdate state NEEDS_RUN was added, which is considered a
|
~ | | pending StatusUpdate for the purposes of collapsing / summaries. |
| ~ | Adds a new StatusUpdate state NEEDS_RUN which represents the ability
|
| ~ | to be run manually on user interaction in a review request, and is
|
| + | considered a pending StatusUpdate for the purposes of collapsing /
|
| + | summaries. |
| |
|
~ | | NEEDS_RUN represents a Status Update that has the ability to be run
|
| ~ | Adds a new option to the PUT API for Status Updates that supports
|
- | | manually on user interaction in a review request. |
- | |
|
- | | A new option to the PUT API for Status Updates was added to support
|
| | running a tool attached to a Status Update. This runs a new signal:
|
| | status_update_run_tool , which extensions can hook into to run some
|
| | sort of tool when the user manually hits the run/retry button in the
|
| | review request. |
| |
|
~ | | A new button was added to the front-end to PUT to the new StatusUpdate
|
~ | | API, which checks for updates on newly run tools. |
| ~ | Adds a new button to the front-end to PUT to the new StatusUpdate API,
|
| ~ | which checks for updates on newly run tools. |
| |
|
~ | | The StatusUpdatesEntry model now contains the review request ID to be
|
~ | | passed to a the event handler of these new buttons. |
| ~ | Adds a new field to the StatusUpdatesEntry model containing the review
|
| ~ | request ID to be passed to a the event handler of these new buttons. |