Skip to content
lcmohsenPublic

About

Chrome extension for LambdaCurry Medusa tickets, pull requests, and Currybot

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

2 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 

Repository files navigation

LC Dev

Chrome extension for LambdaCurry Medusa work on lambda-curry/360training and Jira project MI.

  • Open a Jira ticket (1550 or MI-1550)
  • Open the pull request whose title contains that ticket
  • Open a pull request by number
  • Ask Currybot to review: add currybot-review if 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 review or @coderabbitai review on the pull request in the active tab. If that tab is not a pull request, nothing happens

Install

  1. Open chrome://extensions, enable Developer mode, and choose Load unpacked on this folder.
  2. Create a fine-grained GitHub token for lambda-curry/360training with Issues read and write, and Pull requests read.
  3. Open the extension’s Token page and save the token. Jira and “PR by number” work without it.

Shortcut

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.

About

Chrome extension for LambdaCurry Medusa tickets, pull requests, and Currybot

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages