Skip to content

Instantly share code, notes, and snippets.

View Shandelier's full-sized avatar
🦕
take a brake from sitting bro

Karol K Shandelier

🦕
take a brake from sitting bro
22 followers · 73 following
View GitHub Profile
@jonshipman
jonshipman / styles.csv
Created May 5, 2023 20:03
Stable Diffusion Artist Styles
We can make this file beautiful and searchable if this error is corrected: It looks like row 2 should actually have 5 columns, instead of 3 in line 1.
____Artists____,,,,
Aaron Horkey,"style of Aaron Horkey",""
Abbott Handerson Thayer,"style of Abbott Handerson Thayer",""
Abigail Larson,"style of Abigail Larson",""
Adam Hughes,"style of Adam Hughes",""
Adrian Ghenie,"style of Adrian Ghenie",""
Adrian Tomine,"style of Adrian Tomine",""
Adrianus Eversen,"style of Adrianus Eversen",""
Agnes Cecile,"style of Agnes Cecile",""
Agostino Arrivabene,"style of Agostino Arrivabene",""
@jpierson
jpierson / switch-local-git-repo-to-fork.md
Last active December 26, 2022 21:48 — forked from jagregory/gist:710671
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