docs: freeze repo, point to templates org

Each workflow/action now lives in its own repo under the templates org. Tags v1-v3 stay in place for existing consumers. Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-15 21:42:17 +02:00
2 changed files with 21 additions and 0 deletions
@@ -0,0 +1,7 @@
 # CLAUDE.md
 This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
 This repo is **frozen**. Don't add or change workflows here. Its tags `v1` to `v3` must not be moved, because old consumers still pin `@v3`.
 Development continues in the Gitea org `templates`, with one repo per workflow or action. All of them are checked out locally under `/run/media/alex/Data/Sourcecode/git.custom-coding.net/templates/`, and the `CLAUDE.md` there has the details. The README here lists how old `uses:` paths map to the new ones.
@@ -0,0 +1,14 @@
 # resuable-workflows (frozen)
 This repo is **frozen**. Each workflow and action now lives in its own repo in the [`templates`](https://git.custom-coding.net/templates) org and is versioned on its own.
 The existing tags `v1`, `v2` and `v3` stay where they are and won't be moved, so current consumers keep working. Please migrate:
 | Old | New |
 |---|---|
 | `UltimateCoder/resuable-workflows/.gitea/workflows/docker.yaml@v3` | `templates/docker-build/.gitea/workflows/docker.yaml@v1` |
 | `UltimateCoder/resuable-workflows/.gitea/workflows/sonarqube-dotnet.yaml@v3` | `templates/sonarqube-dotnet/.gitea/workflows/sonarqube-dotnet.yaml@v1` |
 | `https://git.custom-coding.net/UltimateCoder/resuable-workflows/actions/replace-build-vars@v3` | `https://git.custom-coding.net/templates/replace-build-vars@v1` |
 | | `templates/dotnet-build-test/.gitea/workflows/dotnet-build-test.yaml@v1` (new) |
 Inputs, secrets and behavior are unchanged. Only the path differs.