The lengths people go to not use Vim :-)
Because evil-mode, less far than for avoiding Emacs.
9 comments
The lengths people go to not use Vim :-)
Because evil-mode, less far than for avoiding Emacs.
Is it possible to clone a Github repo and keep the clone in sync automatically, if you don't own the source? If so, you could create a Github Action to publish images as updates are released.
edit: I see suggestions to poll the source. That works, but I was hoping to use a hook to avoid that.
You fork the repo which has a GitHub action that builds the container & publishes it, or if it doesn't, you add it to your fork.
And then you create an action on a schedule [0] which checks upstream for updates, and syncs it to your fork. Mind you that that sync needs to be done with a PAT [1], otherwise that sync (push) will not trigger a new build.
[0] https://docs.github.com/en/actions/writing-workflows/choosin...
[1] https://docs.github.com/en/actions/security-for-github-actio...
> When you use the repository's GITHUB_TOKEN to perform tasks, events triggered by the GITHUB_TOKEN, with the exception of workflow_dispatch and repository_dispatch, will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs. For example, if a workflow run pushes code using the repository's GITHUB_TOKEN, a new workflow will not run even when the repository contains a workflow configured to run when push events occur.
The structure I've done is that my repo only contains my build script, and has a scheduled CI job that checks upstream for changes (and builds as needed)
I thought this would let you run some version of edit.com
This is stupid. You are supposed to wait 2 more decades and acquire nano for 26.2 billion dollars once it's as big as Linkedin.
MS Edit in the house! /s