[nikeee]

I use GitHub actions for simple, text-only posts.

I set up an action that gets dispatched once an issue with the label "post" is opened. It then takes that, creates a markdown file with that content and creates a commit. The original issue is then closed.

For more convince, I also have an issue template called "Blog Post", which has already the label set etc. Then, you can bookmark/pin a link to the new issue on your phone's home screen.

I found myself using that instead of git, even if I have a fit client and the repository already cloned.

Currently, it does not support issues where the "post" label is added after issue creation (would be useful for drafts). But it would be entirely possible, as well as image/media/file support.

[pickledish]

Hey this sounds like a really clever solution, actually, would love to look at it — do you have a link to the action, or have you not released it?

[nikeee]

It is not available in public, since it's only a workflow in a private repository that uses four different actions in that order:

- actions/checkout

- A script that edits/changes a file based on the content of the opened issue

- stefanzweifel/git-auto-commit-action@v4

- peter-evans/close-issue@v1

One could make a fully-fledged action out of that. But for my case, this is sufficient.

I also tried a different way, which may also work for you: There are .devcontainers, which can be used for GitHub Code Spaces. It's basically a VSCode in the browser, including a terminal. You can specify which extensions have to be installed, like a spell checker or markdown formatter and use that VSCode in the browser to write posts.

I'm currently not using that because it doesn't work on mobile at all.