git archive --format=tar.gz -o /tmp/my-repo.tar.gz --prefix=my-repo/ master
More detailed version: https://til.simonwillison.net/git/git-archive
#!/bin/bash | |
OAUTH2_TOKEN=<fill in your own OAUTH2 token> | |
OWNER=tiesmaster | |
REPO=Coolkit.Converters # retrieve this with: basename $(git config --get remote.origin.url) .git | |
curl https://api.github.com/repos/${OWNER}/${REPO}/branches/master \ | |
-H "Authorization: token $OAUTH2_TOKEN" \ | |
-H "Accept: application/vnd.github.loki-preview+json" \ |
git archive --format=tar.gz -o /tmp/my-repo.tar.gz --prefix=my-repo/ master
More detailed version: https://til.simonwillison.net/git/git-archive
#!/usr/bin/python | |
""" | |
Python script to connect to an abstract unix socket created by X11 and send arbitrary key-strokes. | |
Created by: [email protected] | |
Credits to: https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/unix/x11/x11_keyboard_exec.rb | |
Borrowed heavily from the original metasploit module. Thanks! | |
""" | |
from socket import * | |
import subprocess |
<?xml version="1.0"?> | |
<!DOCTYPE fontconfig SYSTEM "fonts.dtd"> | |
<!-- /etc/fonts/conf.avail/51-noto-color-emoji.conf --> | |
<fontconfig> | |
<selectfont> | |
<acceptfont> | |
<pattern> | |
<patelt name="family"><string>Noto Color Emoji</string></patelt> | |
</pattern> | |
</acceptfont> |
Inspired by dannyfritz/commit-message-emoji
See also gitmoji.
Commit type | Emoji |
---|---|
Initial commit | 🎉 :tada: |
Version tag | 🔖 :bookmark: |
New feature | ✨ :sparkles: |
Bugfix | 🐛 :bug: |
""" | |
Transforms a normal Python file to pep484 annotations using Jedi. | |
Usage: | |
pep484transform.py <file> [-d] | |
Options: | |
-d, --debug Show Jedi's debug output. | |
""" | |
from os.path import abspath |
While the standard 80 character limit for source code can be traced back to the | |
IBM punch card[1] it can still be seen as a good upper bound for how long lines | |
of text should be on modern high definition displays. | |
First thing we must acknowledge is that source code is not read in the | |
traditional sense. Instead developers scan the source using non-linear eye | |
movements[2] or stay fixated in a small area of code while working out the | |
logical details of code being written. The fixation on a single location, even | |
for more than a few seconds, leads to a loss of visual accuity. Which occurs | |
when the eyes do not perform frequent saccadic eye movements.[3] Further |
This document attempts to refine Python's PEP 440 to include the principles of Semantic Versioning.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.