Skip to content

Instantly share code, notes, and snippets.


Gabriel Staples ElectricRCAircraftGuy

View GitHub Profile
ElectricRCAircraftGuy / count_total_project_code_lines_in_sublime
Created January 14, 2018 23:34 — forked from Hexodus/count_total_project_code_lines_in_sublime
Count total code lines in project using Sublime texteditor
View count_total_project_code_lines_in_sublime
// Go to menue:
// find->find in files
// Switch on reg_ex button
// Find:
// Where:
c:\your_folder\,*.php,*.phtml,*.js,*.inc,*.html, -*/folder_to_exclude/*
// Then click on the find button
// Be careful to not click on Replace!!!
ElectricRCAircraftGuy /
Last active September 15, 2023 11:20 — forked from jpierson/
How to move to a fork after cloning

If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.

To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.

  1. Clone some repo (you've probably already done this step).

    git clone git@github...some-repo.git