You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the refactor of the automation UX, we have "commit" as the action in place of deploy, but behind the scenes it is doing more than a commit and sends the triggers and hooks as well.
For consistency, we should make the commit action only commit changes to a script, and allow the user to make changes to triggers separately. These should just auto-save.
We will need to think through the UI, but some kind of spinner and notice that changes have been saved when a user interacts with the trigger UI is a good start.
The text was updated successfully, but these errors were encountered:
After the refactor of the automation UX, we have "commit" as the action in place of deploy, but behind the scenes it is doing more than a commit and sends the triggers and hooks as well.
For consistency, we should make the commit action only commit changes to a script, and allow the user to make changes to triggers separately. These should just auto-save.
We will need to think through the UI, but some kind of spinner and notice that changes have been saved when a user interacts with the trigger UI is a good start.
The text was updated successfully, but these errors were encountered: