Skip to content

Instantly share code, notes, and snippets.

View lewxdev's full-sized avatar
:shipit:

J. Lewis lewxdev

:shipit:
View GitHub Profile
@0xjac
0xjac / private_fork.md
Last active July 1, 2025 19:06
Create a private fork of a public repository

The repository for the assignment is public and Github does not allow the creation of private forks for public repositories.

The correct way of creating a private frok by duplicating the repo is documented here.

For this assignment the commands are:

  1. Create a bare clone of the repository. (This is temporary and will be removed so just do it wherever.)

git clone --bare [email protected]:usi-systems/easytrace.git

@mrliptontea
mrliptontea / Good commit messages.md
Created March 5, 2019 11:00
Writing good commit messages

Good commit messages serve at least three important purposes:

  • To speed up the reviewing process.
  • To find out what changed in a range of commits (e.g. for a release note).
  • To help the future maintainers, say five years into the future, to find out why a particular change was made to the code or why a specific feature was added.

Structure your commit message like this:

git commands

what I've picked up over the years about the stupid content tracker

🚽 porcelain

git clean -dfx [<path>...]