···99| knot | hostname of the tangled knot used | tangled.sh |
1010| ssh-key | contents of a private ssh key that has push access to the repo | (required) | `-----BEGIN OPENSSH PRIVATE KEY-----\n you really thought, huh? \n-----END OPENSSH PRIVATE KEY-----`
11111212+## Quickstart
1313+1414+1. Create a secret named `TANGLED_KEY` that has your SSH private key
1515+1616+Quick copy if you've created a key with just `ssh-keygen` without any flags:
1717+1818+(linux)
1919+2020+```
2121+wl-copy < ~/.ssh/id_ed25519
2222+```
2323+2424+(mac os)
2525+2626+```
2727+pbcopy < ~/.ssh/id_ed25519
2828+```
2929+3030+(wind*ws)
3131+3232+```
3333+cat ~/.ssh/id_ed25519 > clip.exe
3434+```
3535+3636+Go to your github repo's settings > secrets > actions > repository secrets
3737+3838+2. Create the tangled.sh repo (for now, you have to do it manually beforehand)
3939+4040+3. Just put ~~the fries in the bag~~ this in `.github/workflows/tangle.yml`
4141+4242+```yaml
4343+name: Tangle
4444+4545+on:
4646+ push: {}
4747+ workflow_dispatch: {}
4848+4949+jobs:
5050+ tangle:
5151+ runs-on: ubuntu-latest
5252+ steps:
5353+ - uses: gwennlbh/to-tangled@v0.3
5454+ with:
5555+ repo: yourself.bsky.social/your-repo
5656+ ssh-key: ${{ secrets.TANGLED_KEY }}
5757+```
5858+1259## How?
13601461The action clones your repo, sets up the ssh key, adds the knot as a git remote, and pushes with [`git-push --mirror`](https://man.archlinux.org/man/git-push.1#:~:text=refs/heads/foo%20doesn%E2%80%99t%20exist.-,%2D%2Dmirror,-Instead%20of%20naming)