Initialize public Stash handbook and feature navigation

jamditis committed 2026-10-16 20:46:10 +00:00
commit 094169dbcd
1 file changed
+33
+33
@@ -0,0 +1,33 @@
# Stash handbook
Stash is a public workbench for small experiments, tools, and ideas. Use this wiki for orientation and shared working notes; keep instructions that must travel with code in the repository itself.
## Find your way around
- [Code](https://git.inference.coop/jamditis/stash): files, branches, history, and the README.
- [Issues](https://git.inference.coop/jamditis/stash/issues): reproducible problems and bounded ideas.
- [Pull requests](https://git.inference.coop/jamditis/stash/pulls): proposed changes, discussion, and review.
- [Stash workbench](https://git.inference.coop/jamditis/stash/projects/1): a Kanban board for tracking work.
- [Actions](https://git.inference.coop/jamditis/stash/actions): automation runs when workflows and a compatible runner are available.
- [Releases](https://git.inference.coop/jamditis/stash/releases): deliberate versioned milestones and downloadable artifacts.
- [Packages](https://git.inference.coop/jamditis/stash/packages): software package registry links; no packages are published yet.
## A lightweight workflow
1. Describe the idea or problem in an issue. Keep it small enough to evaluate.
2. Add the issue to the workbench. Backlog is for uncommitted ideas; To Do is selected work; In Progress means active work; Review means a result is ready to inspect; Done means the agreed scope is complete.
3. Make code or documentation changes on a branch and open a pull request.
4. Record checks that actually ran, including limitations.
5. Review and merge deliberately. Publish a release only when there is a meaningful version to distribute.
## Current setup
As of October 16, 2026, repository Actions are enabled, but the runner settings show no available runners. No automated build or test result is claimed. The initial README and contribution templates are proposed in [PR #1](https://git.inference.coop/jamditis/stash/pulls/1).
## Public material only
Do not put credentials, private correspondence, personal records, or internal work files in the wiki, issues, attachments, or code. Use synthetic examples and retain source credits and license notices.
## More about Gitea
[Official documentation](https://docs.gitea.com/) explains the platform. Features supported by Gitea do not by themselves establish the hosting co-op's quotas, runner availability, or pricing.