#forgejo doesn't offer something comparable to gists on Github. But that actually allows for a better solution. You cannot create pull requests on gists over on GitHub for "reasons". Which is a bit of a shame.
So I created a repo called "gists" on @Codeberg (which runs on Forgejo) and filled it with, well, gists. So now you can simply read them, clone the repo and create pull requests if you think I said something that needs a bit of correction.
Every gist is stored with the creation date in the name. So you can immediately see how old and possibly outdated something is. I do keep them updated, though. So they all should work regardless of when I posted them the first time. You can check the revisions to see all details.
@jwildeboer I like gist because they are a quick way with no friction to share snippets of code or to be a quick space for keeping useful commands. Creating a repository for them or storing them in a single standard repository for some reason makes me lazy and annoyed. Sometimes if something I have there grows, I proceed to copy it in a dedicated repository.
Add comment