#4.9 / 10 rate

Kamino

679 users

2019-08-02

John Murphy

[email protected]

Extension Information

5 star

86%

4 star

14%

3 star

2 star

1 star

Supported Languages

Permissions

Hot Permissions

Description

This extension shows a button on Github issue pages that can be used to clone github issues across repositories

Kamino is a Chrome extension that is used to clone Github issues from one repository to another. Go to an issue page and click "Clone issue to", choose a new repository and the original item will be closed and cloned to the new repository you have chosen. This tool is very handy for feedback repositories whose issues need to be distributed to the actual project repository.

For detailed instructions and info on updates, please visit https://github.com/gatewayapps/kamino and view the ReadMe file.

kamino v4.1.0
- Bug Fix: Fixed an issue with CSS that was causing Github styling to break on the PR page
- Bug Fix: Hopefully fixed the manifest issue with CDNs
- Feature: When cloning from a forked repo, Kamino should now work
- Feature - Add option to prevent references to cloned issue
- Feature - Cloned items/comments now are better formatted
- Miscellaneous: Cleaned up code using code formatter

Release generated by Parcel(https://parcelapp.io)

Reviews

malkit benning

Works great for me, it really speeds up bringing across issues from my tutor's repo to my own. Some of the students are not able to see/copy labels across, and I can't see an option to help them. Hopefully John Murphy will be able to help solve the mystery?

Hung Vu

Good extension.

Ben Haynes

A useful tool for copying the title, labels, and original message to a new repo. I would make two recommendations: 1. There should be an option to copy over an issue's comments too. 90% of our info is in the comments, and it makes it impossible to "continue" a dialog if you always have to link back to the original ticket to see context. Comments could either get added as actual comments, or (if that's not possible) using some syntax in the main message. eg: delineated by a markdown HR, commenter's username, and datetime commented: ``` ---- @[commenter's name] – 2018-01-01 12:00:00 ``` 2. The only other option would be @mention each user (original and from comments) so they are added to the participants list and get updates on the new ticket. A great tool, and if the above two features were added this would be pretty much perfect! Thank you John!