Skip to content

Instantly share code, notes, and snippets.

View sandman's full-sized avatar
:electron:
Exploring

sandman

:electron:
Exploring
View GitHub Profile

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
@sandman
sandman / [OpenWRT] UBOND Example
Created April 25, 2023 10:08 — forked from TalalMash/[OpenWRT] UBOND Example
[OpenWRT] UBOND Example
Download binaries: https://github.com/TalalMash/ubond/releases/tag/v0.1.1
Disable encryption for 400Mbit+ , force DNS over HTTPS if needed.
Temporarily running as root. (tun bugfix TODO)
----------------------
VPS/crontab -e:
@reboot screen -d -m sh -c "/root/startubond.sh"
----------------------
/root/startubond.sh
----------------------
#!/bin/sh
@sandman
sandman / README.md
Last active February 11, 2021 18:57 — forked from corenel/README.md
Install NVDEC and NVENC as GStreamer plugins

Install NVDEC and NVENC as GStreamer plugins

Environment

  • Ubuntu 18.04
  • NVIDIA driver 430.40
  • NVIDIA Video Codec SDK 9.0.20

Steps