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
Currently, the UX for manually triggering Vibinex on a pull request is sub-optimal. The user has to copy the link of the pull request (which also has to be the root link of the pull request), paste it into the popup window (right next to the "Logout" button) and then click "Trigger".
A much better UX would be to have a button on the pull request page that can just be clicked to trigger Vibinex.
Optional: Show different states of the button:
Default: The button is ready to be clicked with the Vibinex refresh symbol, and the tooltip text "Process this PR on Vibinex".
Highlighted: If the pull request is not processed even once before, change the styling of the button to highlight it more.
On Click: As soon as the user clicks the button, it should become disabled and the text should change to "Triggering..."
Processing: Once the trigger is successful, the button should still be disabled, but the color should change to a shade of green and the text should change to "Processing...".
Done: Once the hunks table row for the pull request has a last_modified_at timestamp greater than the time of the click, we can change the text of the button to "Done!". Then we can either refresh the page or just trigger the UI update function again. The button should change back to the "Default" state once the UI is updated.
The text was updated successfully, but these errors were encountered:
Currently, the UX for manually triggering Vibinex on a pull request is sub-optimal. The user has to copy the link of the pull request (which also has to be the root link of the pull request), paste it into the popup window (right next to the "Logout" button) and then click "Trigger".
A much better UX would be to have a button on the pull request page that can just be clicked to trigger Vibinex.
Optional: Show different states of the button:
disabled
and the text should change to "Triggering..."hunks
table row for the pull request has alast_modified_at
timestamp greater than the time of the click, we can change the text of the button to "Done!". Then we can either refresh the page or just trigger the UI update function again. The button should change back to the "Default" state once the UI is updated.The text was updated successfully, but these errors were encountered: