Closed avikalpg closed 1 month ago
Hi @avikalpg , I am ready to work on it can you assign me now?
Hi @harith-aaron, thanks for your interest. Before I assign the issue to you, can you describe your approach to resolving this issue?
I can assign the issue to you once we agree on your approach (and hopefully the LLD).
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.