Kamino

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

Kamino - Clone GitHub Issues Easily

"Kamino" is a Chrome extension designed to streamline the process of cloning GitHub issues from one repository to another. By simply navigating to an issue page and using the 'Clone issue to' button, you can easily select a new repository. The original issue is closed and duplicated in the chosen location, making it an invaluable tool for managing feedback repositories that require issue distribution. With its latest update, Kamino ensures improved functionality and user experience.

Download

Extension stats

By: John Murphy

Users: 697

-8

Rating: 4.90

(10)

Version: 4.1.2 (Last updated: 2025-01-05)

Creation date: 2019-08-02

Risk impact: High risk impact

Risk likelihood:

Very low risk likelihood

Manifest version: 3

Permissions:

background
scripting
storage
webNavigation

Host permissions:

*://github.com/*

Size: 579.58K

Email: jo*****@gatewayapps.com

URLs: Privacy policy

Ranking

# 34,681 ▼ 207

Other rankings

#333 in Developer Tools ▼ 3

Other platforms

Not available on Android

Not available on Firefox

Not available on Edge

Want to check extension ranking and stats more quickly for other Chrome extensions? Install Chrome-Stats extension to view Chrome-Stats data as you browse the Chrome Web Store.

Extension summary

Analyze keywords

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.2

bug-fix - Fixed an issue in which the Kamino button would not appear on public repos due to a change in the Github page code. - by @brandonadams5
bug-fix - Fixed an issue in which cloning an issue that didn't have a description would not work - by @brandonadams5

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

User reviews

These summaries are automatically generated weekly using AI based on recent user reviews. Chrome Web Store does not verify user reviews, so some user reviews may be inaccurate, spammy, or outdated.

Pros

Speeds up bringing issues from one repo to another
Useful for copying titles, labels, and original messages
Helps set up feedback options in applications
Makes cloning issues between repos easy
Well-received and simple to use

Cons

Some users cannot see/copy labels
Lacks an option to copy over issue comments
No functionality to @mention users from original comments

Most mentioned

Works great
Easy to clone issues
Helpful for managing issues between repos

User reviews

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?

malkit benning, 2023-05-05

Good extension.

Hung Vu, 2019-03-28

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!