| echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc | |
| . ~/.bashrc | |
| mkdir ~/local | |
| mkdir ~/node-latest-install | |
| cd ~/node-latest-install | |
| curl http://nodejs.org/dist/node-latest.tar.gz | tar xz --strip-components=1 | |
| ./configure --prefix=~/local | |
| make install # ok, fine, this step probably takes more than 30 seconds... | |
| curl https://www.npmjs.org/install.sh | sh |
cribbed from http://pastebin.com/xgzeAmBn
Templates to remind you of the options and formatting for the different types of objects you might want to document using YARD.
Locate the section for your stash remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = git@stash.internal:private/repository.git
Now add the line fetch = +refs/pull-requests/*:refs/remotes/origin/pull-requests/* to this section. Obviously, change the stash url to match your project's URL. It ends up looking like this:
| #!/bin/sh | |
| # vault-merge | |
| # Benjamin Ragheb <ben@benzado.com> | |
| # This shell script handles conflicts generated by attempts to merge encrypted | |
| # Ansible Vault files. Run `git merge` as usual; when git warns of a merge | |
| # conflict, run this command to attempt a merge on the unencrypted versions of | |
| # the file. If there are conflicts, you will be given a chance to correct them | |
| # in $EDITOR. |
| /** | |
| * Sorry if there are some imports or bits missing that are needed | |
| * to make sense of this. I'm copy/pasting from a working example and | |
| * trying to tease out things that are not relevant to push notification | |
| * registration. | |
| */ | |
| import android.app.Fragment; | |
| import android.app.FragmentManager; | |
| import android.content.Context; | |
| import android.content.Intent; |
| # In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env | |
| # variable pointing GPG to the gpg-agent socket. This little script, which must be sourced | |
| # in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start | |
| # gpg-agent or set up the GPG_AGENT_INFO variable if it's already running. | |
| # Add the following to your shell init to set up gpg-agent automatically for every shell | |
| if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then | |
| source ~/.gnupg/.gpg-agent-info | |
| export GPG_AGENT_INFO | |
| else |
This scrapes GitHub's dep graph page to find dependents of a repo, and writes it to a file for processing.
This is useful because GitHub's API doesn't currently support querying dependents, and the page in the UI is not sorted.
pkg.go.dev also shows dependents per-Go-package, including non-GitHub repos, but it's not sorted in any useful way to discover "popular" dependents.
Lines in the output are [repo] [stars] [forks]
It's incomplete and could probably be improved, but it scratches my itch. Feel free to fork it and do what you want.
Although @setup/node as a built-in cache option, it lacks an opportunity regarding cache persistence. Depending on usage, the action below might give you faster installs and potentially reduce carbon emissions (♻️🌳❤️).
Yarn 3+/4+ with nodeLinker: node-modules. (Not using yarn ? see the corresponding pnpm 7/8+ action gist)
