wiki/ with a .publish marker, so the shared scoped Publish wiki workflow publishes four pages (Home, Getting started, SSH and tokens, Troubleshooting) to the Gitea wiki.
.gitea/workflows/quality.yml: shellcheck and shfmt through the shared reusable workflow of TirSystem/github-action, pinned to v1.1.0.
.gitea/workflows/release.yml: manual release (tag and release page from CHANGELOG.md), dry_run on by default.
CHANGELOG.md starter with an [Unreleased] section.
.editorconfig: switch_case_indent = true for *.sh, so shfmt accepts the existing case layout.
Before merging
The wiki is published only if the organization secret TOKEN_FOR_GITEA_WIKI exists in TirSystem-BashScript. After the merge the log should end with Published 4 page(s) to the wiki.
After merging
Run Release once with dry_run true. It requires the Quality run on the commit, whose context is Quality / quality (push); the run on this pull request confirmed the name (Quality / quality (pull_request) is green).
The release workflow keeps a moving major tag, so releasing a 0.x version creates v0.
No issue is closed by this pull request. The wiki page SSH and tokens links to issue 77 (passphrase keys), which stays open.
## What
- `wiki/` with a `.publish` marker, so the shared scoped **Publish wiki** workflow publishes four pages (Home, Getting started, SSH and tokens, Troubleshooting) to the Gitea wiki.
- `.gitea/workflows/quality.yml`: shellcheck and shfmt through the shared reusable workflow of `TirSystem/github-action`, pinned to `v1.1.0`.
- `.gitea/workflows/release.yml`: manual release (tag and release page from `CHANGELOG.md`), `dry_run` on by default.
- `CHANGELOG.md` starter with an `[Unreleased]` section.
- `.editorconfig`: `switch_case_indent = true` for `*.sh`, so shfmt accepts the existing `case` layout.
## Before merging
- The wiki is published only if the organization secret `TOKEN_FOR_GITEA_WIKI` exists in `TirSystem-BashScript`. After the merge the log should end with `Published 4 page(s) to the wiki`.
## After merging
- Run **Release** once with `dry_run` true. It requires the Quality run on the commit, whose context is `Quality / quality (push)`; the run on this pull request confirmed the name (`Quality / quality (pull_request)` is green).
- The release workflow keeps a moving major tag, so releasing a 0.x version creates `v0`.
No issue is closed by this pull request. The wiki page SSH and tokens links to issue 77 (passphrase keys), which stays open.
Add a wiki/ folder with a .publish marker for the shared Publish wiki
workflow, a Quality workflow (shellcheck and shfmt through the shared
reusable workflow) and a manual Release workflow that builds the release
page from CHANGELOG.md.
Set switch_case_indent for *.sh in .editorconfig so shfmt accepts the
existing case layout.
The real context of the Quality run on a push is
"Quality / quality (push)", not the nested job name. Also store the file
with LF line endings, as .editorconfig requires.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
wiki/with a.publishmarker, so the shared scoped Publish wiki workflow publishes four pages (Home, Getting started, SSH and tokens, Troubleshooting) to the Gitea wiki..gitea/workflows/quality.yml: shellcheck and shfmt through the shared reusable workflow ofTirSystem/github-action, pinned tov1.1.0..gitea/workflows/release.yml: manual release (tag and release page fromCHANGELOG.md),dry_runon by default.CHANGELOG.mdstarter with an[Unreleased]section..editorconfig:switch_case_indent = truefor*.sh, so shfmt accepts the existingcaselayout.Before merging
TOKEN_FOR_GITEA_WIKIexists inTirSystem-BashScript. After the merge the log should end withPublished 4 page(s) to the wiki.After merging
dry_runtrue. It requires the Quality run on the commit, whose context isQuality / quality (push); the run on this pull request confirmed the name (Quality / quality (pull_request)is green).v0.No issue is closed by this pull request. The wiki page SSH and tokens links to issue 77 (passphrase keys), which stays open.