Effortlessly copy file paths with their respective line numbers when working on GitHub.
Line Clipper for GitHub Extension
A lot of IDEs provide fuzzy find capabilities so you can specify a file path and the IDE would open that file for you. Additionally, you can specify a line number at which you'd like to go to. Example:
\"api/controllers/base_controller.go:73\"
This would take us to the \"base_controller.go\" file on \"line 73\" in the \"api/controllers\" directory.
When working with GitHub (especially during code reviews) it's common for a developer to jump from the browser to the IDE and vice versa. As it is today this flow is very clunky and can break a developer's flow while working.
The \"LineClipper\" extension focuses on doing one thing and do it well - copy to your clipboard the file path suffixed with the respective line number when clicking on a specific line number while viewing any type of file with line numbering on GitHub. This way a developer can almost instantly go back and forth between browser and IDE when reviewing files and particular points in code all while keeping a developer's focus where it should be - in the code, not in meaningless operational details.
The plugin includes the copying to clipboard functionality when:
- \"reviewing pull requests in the Files Changed tab\"
- \"reviewing pull requests in the Conversation tab where there are file snippets\"
- \"going through a repository's files\"
- \"going through files from old commits\"
Your feedback is valuable so it would be appreciated if you leave a rating or feedback of your experience!
Also if you have ideas for improvement you can go ahead and contribute directly to the project: https://github.com/NickyMateev/Line-Clipper
FAQ:
Q: Why does the extension state upon installation that it can read and change all my data on the websites I visit?
A: \"LineClipper\" will only attempt to work on websites which contain \"github\" as part of their domain. You can check out this in source here (https://github.com/NickyMateev/Line-Clipper/blob/3f13ab4063e2f72e9860e974d3ec58ee1dda0306/manifest.json#L8).
The reason for deciding to work on all domains containing \"github\" is that often developers work with multiple public/private installations of GitHub. Out of convenience for the developer it was decided to simply match these domains automatically instead of having to make the developer whitelist every single GitHub domain he works in.
Q: Does the extension work for all GitHub installations or just the public https://github.com installation?
A: The extension, as stated above, works on all kinds of GitHub installations public/private as long as the domain contains
the word \"github\" in it.
Q: Does this work only when traversing a GitHub project's file tree and looking at different files?
A: No, it works for every page on GitHub which has a file with lines in it. You can copy lines from
the GitHub Pull request diff perspective when you're looking at the file diffs or at the main page of a
pull request where sometimes we see some code snippets which have been commented. You can also copy line numbers
when you're going through old commits and looking around at the files.
PLEASE NOTE:
\"LineClipper\" (also known as \"Line Clipper for GitHub\" in the Chrome Web Store) is not endorsed by GitHub.
GitHub and Google Chrome are trademarks of their respective owners.
Source Manifest.json
How to download and manually install Line Clipper for GitHub extension for Chrome
Looking for a way to install Line Clipper for GitHub extensions for Chrome, you can search for them in the Chrome Web Store, clicking the "Add to Chrome" button, and following the straightforward process.
However, you may need to install Line Clipper for GitHub extensions manually, this article outlines two simple methods to effortlessly install Line Clipper for GitHub extensions, whether they come as unpacked folders in compressed formats like .zip or as .crx files.
Method 1: Download Line Clipper for GitHub extension and manually install through Drag &Drop
If you ever need to manually install a Line Clipper for GitHub extension for Chrome, don't worry, it's a simple process. Just follow these easy steps, and you will have your extension ready to use in no time.
Step 1: Download the Line Clipper for GitHub Extension by clicking the "Download CRX" button on the website.
Look for the Line Clipper for GitHub extension you wish to install. Go to the website and download the Line Clipper for GitHub extension package, which is usually a .CRX file and comes in a zipped file. Here ".crx" file is the format for Line Clipper for GitHub extension that contains all the data.
Step 2: Extract &Arrange Files
Once the file is downloaded, extract that file into its own folder. Similarly, give that extension files a permanent home. In other words, keep it in a folder that you don't accidentally delete it because these files will be needed to make that extension work.
Step 3: Go to the Chrome Extensions Page
Open Google Chrome and in the address bar, type chrome://extensions; it will open the Google Chrome extensions page. Make sure that "My extensions" is selected in the sidebar.
Step 4: Drag and Drop the Extension
Now, go to the folder where you extracted the Line Clipper for GitHub extension and drag &drop the extension file from there anywhere onto the extension page within Google Chrome.
Step 5: Complete the Installation
Once you drag and drop the extension file, follow the steps that Google Chrome takes you through. Similarly, if the extension file is of .crx file format, you will be required to review the permissions and then add the extension.
Now, you can manage that added extension as you would like to with any other Chrome extension that you added through Chrome Webstore. Its icon will also appear in the Google Chrome Menu on the right side of the address bar once you activate it.
Method 2: Download Line Clipper for GitHub extension for Chrome and install in Developer Mode
This is another method to install Line Clipper for GitHub extension manually, but the twist is that here, you install by enabling the developer mode option provided in Google Chrome. This mode is commonly used for testing extensions or running unpublished tools.
Step 1: Download the Line Clipper for GitHub extension file
Select and download the Line Clipper for GitHub extension by clicking the 'Download CRX' button on the website.
Step 2: Extract the downloaded contents
Convert the file to a ZIP file if it is in CRX format then extract the Line Clipper for GitHub extension zip file or folder that you downloaded. Make sure you extract it using the same folder name and keep it safely in another folder, so you don't delete it by mistake. The extracted folder will be needed to keep your Line Clipper for GitHub extension running.
Step 3: Open Chrome Extension Setting Page
In the address bar of Google Chrome, type chrome://extensions and open the Chrome Extension Page.
Step 4: Enable Developer Mode
After opening the Chrome Extension page, look at the top right side, and you will find the toggle option of "Developer mode."Simply enable that developer mode option.
Step 5: Load the Unpacked Extension
Once you enable the developer mode option, you will see the menu of Load Unpacked, Pack Extensions and Update. From that, select the option "Load unpacked."
Step 6: Select the Extension Folder
Once the pop-up opens upon clicking Load unpacked, select the Line Clipper for GitHub extension directory and click on the "Select Folder "button.
Step 7: Confirm and Install
After you select an extension folder of a Google Chrome extension you're installing manually, confirm its installation for the final time and let the installation complete.
Conclusion
Here we've made a step-by-step guide on How to manually install Line Clipper for GitHub extension in 2 ways. We hope this guide proves helpful.
Similar Extensions
GitHub Monitor 42 0 ★ 36.81KiB
Pages2Repo 42 3 ★ 213KiB
Friendly GitHub 42 2 ★ 44.63KiB
Codeflower 42 2 ★ 246KiB
HubLighter - GitHub Code Highlighter 42 2 ★ 58.39KiB
github-php-function-jumper 42 2 ★ 11.38MiB
Refined GitHub Notifications 42 0 ★ 15.27KiB
Github Annotator 42 2 ★ 81.68KiB
Simply GIT 42 7 ★ 224KiB
Git flow (for Github) 42 1 ★ 218KiB
OctoLenses 42 3 ★ 3.74MiB
Open Github/Bitbucket in editor 42 0 ★ 50.72KiB

OctoEdit 42 0 ★ 1.16MiB
github-find 42 1 ★ 40.7KiB

console.sparkline 42 1 ★ 4.7KiB

Github Code Outline 42 1 ★ 464KiB

Nodei.co: npm badges for GitHub 42 6 ★ 24.33KiB
github-readme-toc 42 2 ★ 2.22MiB
Builds Tab for Github 42 0 ★ 160KiB
The-M-Project Inspector 42 4 ★ 12.79KiB
MultitaskOS 42 1 ★ 2.85MiB
github npm stats 42 4 ★ 65.86KiB
Github Super Search 42 0 ★ 46.74KiB
Github Sidebar 42 2 ★ 562KiB