Chrome extension for LambdaCurry Medusa work on lambda-curry/360training and Jira project MI.
- Open a Jira ticket (
1550orMI-1550) - Open the pull request whose title contains that ticket
- Open a pull request by number
- Ask Currybot to review: add
currybot-reviewif it is missing, otherwise comment@currybot-lc re-review please - Ask Currybot to review the pull request in the active tab. If that tab is not a pull request, nothing happens. With no token, it uses the page: add
currybot-review, or comment if that label is already there - Comment
@coderabbitai full reviewor@coderabbitai reviewon the pull request in the active tab. If that tab is not a pull request, nothing happens
- Open
chrome://extensions, enable Developer mode, and choose Load unpacked on this folder. - Create a fine-grained GitHub token for
lambda-curry/360trainingwith Issues read and write, and Pull requests read. - Open the extension’s Token page and save the token. Jira and “PR by number” work without it.
Ctrl+Shift+. opens a numbered menu on normal web pages. Press a number to type a ticket or PR, Enter to run it, Esc to dismiss. Any other key closes the menu. An invalid value shows an error and leaves the field open. The shortcut does nothing while focus is in a text field. It does not run on chrome:// pages or the new tab; use the toolbar button there.
node src/actions.test.js checks ticket parsing and the Currybot label-vs-comment choice.