4 ms·
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?
by pickledish 5y ago
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 5y agoIt 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.