@bensandee/forgejo-cli 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Orange Bike Labs, LLC
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,52 @@
+# @bensandee/forgejo-cli
+
+`bst-fj`: the Forgejo API commands, without the rest of `bst`. These commands used to ship on
+`@bensandee/tooling`'s `bst` bin.
+
+## Installation
+
+```bash
+pnpm add -D @bensandee/forgejo-cli
+
+# Or run directly
+pnpm dlx @bensandee/forgejo-cli --help
+```
+
+## Connection
+
+Every command finds its repository and token the same way `bst` does. It reads the environment
+first:
+
+| Variable             | Meaning                                                    |
+| -------------------- | ---------------------------------------------------------- |
+| `FORGEJO_SERVER_URL` | The forge's base URL, such as `https://codeberg.org`       |
+| `FORGEJO_REPOSITORY` | The target repository as `owner/repo`                      |
+| `RELEASE_TOKEN`      | The API token (`FORGEJO_TOKEN` is used when this is unset) |
+
+When the server URL or repository is not set, it falls back to the `origin` git remote, then to
+`package.json#repository`. A command that takes `--repo` targets that repository instead.
+
+## Environment file
+
+Set `BST_ENV_FILE` to the path of an env file, and `bst-fj` loads it before anything else runs, the
+same way `bst` does. A variable already set in the environment always wins over the file. A file
+that cannot be read stops the command before it starts. This is for development only: a production
+run should get every variable from its environment and leave `BST_ENV_FILE` unset.
+
+## Commands
+
+Run `bst-fj --help` for the list and `bst-fj <command> --help` for each command's flags. Every
+command takes `--json`, which prints exactly one JSON document, failures included.
+
+| Command          | What it does                                                                                               |
+| ---------------- | ---------------------------------------------------------------------------------------------------------- |
+| `labels`         | `list` a repository's labels, or `sync` one named set from a `--file` (creates and updates, never deletes) |
+| `secrets`        | `set`, `list` or `delete` Forgejo Actions secrets                                                          |
+| `webhooks`       | List webhooks across an instance (system, user, org and repo)                                              |
+| `release:create` | Create a release for a tag the forge already has; refuses a tag the forge lacks unless given `--target`    |
+| `pr:checks`      | Read a pull request's CI verdict, optionally `--wait` for it to settle                                     |
+| `pr:list`        | List a repository's pull requests                                                                          |
+| `commit:status`  | Read the status checks for a commit SHA, branch, tag or git ref                                            |
+
+Zero posted statuses reads as `no-status`, never as green. Every command is Forgejo-only: on
+GitHub, use `gh`.

package/bin/bst-fj.mjs

@@ -0,0 +1,25 @@
+#!/usr/bin/env node
+/**
+ * Stable bin target for `bst-fj`.
+ *
+ * This file exists only so that `node_modules/.bin/bst-fj` can be created, and it is committed
+ * rather than built for exactly that reason. pnpm links bins **during install**, and skips one
+ * whose target is missing -- so pointing `bin` straight at `dist/bin.mjs` works only in a tree
+ * that already happens to be built. A fresh checkout installs before it builds, pnpm warns
+ * (`Failed to create bin ... ENOENT`) and moves on, and building afterwards does not go back and
+ * create the link. Every later `pnpm exec bst-fj` then fails with `Command "bst-fj" not found`.
+ *
+ * The indirection costs one module load and makes the bin link independent of build state: the
+ * link always exists, and `dist/bin.mjs` only has to be there by the time someone runs it. When
+ * it is not, the failure is an explicit ERR_MODULE_NOT_FOUND naming the missing build output --
+ * a far better error than a command that appears not to exist.
+ *
+ * Consumers installing from the registry get both files (`files` ships `bin` and `dist`) and are
+ * unaffected either way, since a published tarball is always built.
+ *
+ * Loaded with a dynamic `await import` rather than a bare `import "../dist/bin.mjs"`, which is an
+ * unassigned import and trips `import(no-unassigned-import)`. Suppressing that rule would be the
+ * wrong trade for a file whose entire purpose is a side effect: the dynamic form says "run this"
+ * rather than "bring in these bindings", which is what is actually meant here.
+ */
+await import("../dist/bin.mjs");