coulomb/whynot-design
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Migrate npm and git refs to Forgejo (RAIL-HO-WP-0006)
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 20s
Details

Browse source
This commit is contained in:
tegwick 2026-07-09 11:59:08 +02:00
parent 8c24e44857
commit 6de4d31bde
5 changed files with 10 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

2
DesignSystemIntroduction.md
View file

@ -345,7 +345,7 @@ This staging is exactly the *"low-cost learning first"* posture in `whynot-contr
For whoever is bootstrapping this repo right now:
- [ ] Push the seed contents to `gitea.coulomb.social/coulomb/whynot-design`.
- [ ] Push the seed contents to `forgejo.coulomb.social/coulomb/whynot-design`.
- [ ] Cut the first real tag with `make release VERSION=x.y.z` (see §6 — *Release ritual*) so consumers can pin.
- [ ] Add the repo as a remote dependency in **one** consuming app (the Django one) and verify imports work end-to-end. Follow [`MultiFrameworkSupport.md` §Django](./MultiFrameworkSupport.md#django-server-rendered-templates--htmx).
- [ ] Open one trivial PR against `whynot-design` (e.g. a CHANGELOG typo) to confirm CI passes end-to-end.