@doikayt/typescript-build-config 0.1.37 → 0.1.39

package/README.md

@@ -32,6 +32,7 @@ Shared build configuration presets for TypeScript-based projects.
   - [For Maintainers](#for-maintainers)
     - [Clone and install](#clone-and-install)
     - [Run the full CI suite](#run-the-full-ci-suite)
+    - [Test the shell aliases](#test-the-shell-aliases)
   - [License](#license)
 <!-- TOC:END -->
 
@@ -537,6 +538,10 @@ On `npm update`, the behavior per file is:
 This means local customisations are never silently overwritten, but you are
 notified when your copy has drifted from the upstream version.
 
+**Where to see pipeline runs:** Codeberg's repository page has no GitHub-style "Actions" tab.
+Runs are listed on Woodpecker at `https://ci.codeberg.org/repos/<repo-id>`; see
+[Finding `<repo-id>` and `<org-id>`](CODEBERG_HOW_TO_ARTICLE/onboarding-a-new-user.md#finding-repo-id-and-org-id).
+
 The release pipeline requires `NPM` and `CODEBERG_TOKEN` secrets in Woodpecker.
 
 ## Conventions Every Project Must Adhere To
@@ -663,11 +668,12 @@ Installed by [Quick start](#quick-start) step 1 (or manually: add
 
 | Alias | What it does |
 | --- | --- |
-| `mkrepo <name>` | Create a public repo in the `doikayt` org (guards against duplicates). |
+| `mkrepo <name>` | Create a public repo in the `doikayt` org (guards against duplicates). Needs a team with **Create repositories**; see [Teams](CODEBERG_HOW_TO_ARTICLE/orgs-teams-and-members.md#teams). |
+| `rmrepo <name>` | Permanently delete a repo from the `doikayt` org. Shows what it found, then makes you type the full `owner/name` to confirm; there is no flag to skip that. |
 | `addpush [name]` | Wire up the current directory to an existing Codeberg repo (create it first with `mkrepo`) and push. Defaults `name` to the current directory. |
 | `dk-new` | `npm init -y` + `@doikayt` scope. |
 | `dk-init` | Scaffold the build config into the current project. |
-| `dk-scaffold <name>\|. [lib\|app] [--local] [-q]` | Create the repo, scaffold, and push — one command (defaults to app). Pass `.` to scaffold in the current directory, using its leaf name as `@doikayt/<package-name>`. `--local` skips the repo and push; `-q` hides the auto-answered-prompts note. |
+| `dk-scaffold <name>\|. [lib\|app] [--local] [-q]` | Create the repo, scaffold, and push — one command (defaults to app). Pass `.` to scaffold in the current directory, using its leaf name as `@doikayt/<package-name>`. `--local` skips the repo and push; `-q` hides the auto-answered-prompts note. Without `--local` it needs a team with **Create repositories**; see [Teams](CODEBERG_HOW_TO_ARTICLE/orgs-teams-and-members.md#teams). |
 | `gp` | Pull with rebase, then push the current branch. The everyday git sync command — requires the branch to already track a remote. |
 | `gpu` | First push of a new local branch: sets it up to track `origin` and pushes (or just wires up tracking if `origin` already has a same-named branch). |
 | `trackify` | Set the upstream tracking branch for the current branch to the same-named branch on `origin`, without pushing. Fails if that remote branch doesn't exist yet. |
@@ -707,6 +713,39 @@ To auto-fix formatting before verifying:
 npm run update-all-format && npm run ci
 ```
 
+### Test the shell aliases
+
+The tests for `assets/shell/aliases.sh` live in `tests/aliases.test.js`. Most of them run
+the aliases in a bash subprocess with `curl` replaced by a stub, so they make no network
+calls and can't touch Codeberg. `npm test` and `npm run ci` run them with everything else.
+
+**When to run them:** after any change to `aliases.sh`, and before a release that touches
+`mkrepo`, `rmrepo`, or `dk-scaffold`.
+
+To run only the `rmrepo` tests:
+
+```bash
+node --test --test-name-pattern='rmrepo' tests/aliases.test.js
+```
+
+**Live test (opt-in).** One test, `live: mkrepo then rmrepo round trip`, calls the real
+Codeberg API. It creates a repo named `tbc-livetest-<timestamp>` in your org and deletes it
+again, with a cleanup in a `finally` block if something fails partway. It is skipped
+unless `RUN_LIVE_CODEBERG_TESTS=1`, `CODEBERG_TOKEN` and `REPO_OWNER` are all set, so
+`npm test` never runs it. Run it once, by hand, after changing `mkrepo` or `rmrepo`:
+
+```bash
+export CODEBERG_TOKEN=<your token>
+export REPO_OWNER=doikayt
+NO_COLOR=1 RUN_LIVE_CODEBERG_TESTS=1 node --test --test-name-pattern='live' tests/aliases.test.js
+```
+
+- The token needs `repository` and `organization` Read and write, and your account must be
+  on a team with **Create repositories** (see
+  [access-tokens.md](CODEBERG_HOW_TO_ARTICLE/access-tokens.md)).
+- `NO_COLOR=1` keeps the summary lines readable on terminals that render Node's grey
+  "bright black" as near-invisible. It is optional.
+
 To verify end-to-end that `init` scaffolds and ships both a library and an app —
 by hand, with what to look for at each step — follow
 [docs/verification-runbook.md](docs/verification-runbook.md).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@doikayt/typescript-build-config",
-  "version": "0.1.37",
+  "version": "0.1.39",
   "description": "Shared build configuration for TypeScript projects — ESLint, Prettier, tsconfig, and Playwright presets",
   "_comments": {
     "exports": "This block lists the config files that will be extended by files in in src/toplevel - which are copied to consuming project root folder. An example: eslint.config.js imports from '@doikayt/typescript-build-config/eslint'.",