fix: fall back to github token for release please (#19)

Author: dkarter

.github/workflows/release.yml

@@ -16,6 +16,6 @@ jobs:
       - name: Release Please
         uses: googleapis/release-please-action@v5.0.0
         with:
-          token: ${{ secrets.RELEASE_PLEASE_GITHUB_TOKEN }}
+          token: ${{ secrets.RELEASE_PLEASE_GITHUB_TOKEN || github.token }}
           config-file: release-please-config.json
           manifest-file: .release-please-manifest.json

docs/DEVELOPMENT.md

@@ -0,0 +1,52 @@
+# Development
+
+## Stacked PRs
+
+Use the local `stack` CLI for stacked PR maintenance in this repository. It is built for squash-merge
+repositories where merged branches are deleted, so Git ancestry alone cannot preserve stack intent.
+
+Use plain `git` for normal editing and commits. Use `stack` for stack inspection, PR-base syncing, safe
+merges, and undo workflows.
+
+Common commands:
+
+```sh
+stack status
+stack guide
+stack sync --dry-run
+stack sync
+stack sync --keep-going
+stack merge
+stack merge --apply
+stack merge --auto
+stack history
+stack undo
+stack undo --apply
+```
+
+Preferred stacked PR flow:
+
+```sh
+gh pr create --base main --head stack-a
+gh pr create --base stack-a --head stack-b
+stack sync --dry-run
+stack sync
+```
+
+Use `stack sync --dry-run` before mutating stack metadata or retargeting PRs. If the preview is correct,
+run `stack sync` to infer PR-base stack links, repair descendants, retarget PRs, and refresh stack blocks in
+PR descriptions.
+
+Use `stack merge` without flags as a dry run. Add `--apply` only after the plan looks correct. Use
+`stack merge --auto` when GitHub auto-merge should land the root PR and then repair descendants.
+
+If a stack operation needs to be reverted, inspect the latest repair journal first:
+
+```sh
+stack history
+stack undo
+stack undo --apply
+```
+
+Do not edit `.git/stack/state.json` by hand. If local stack metadata looks stale, run `stack sync --dry-run`
+and then `stack sync` if the inferred stack is correct.

docs/RELEASE.md

@@ -3,8 +3,8 @@
 Releases are managed by [release-please](https://github.com/googleapis/release-please) through
 `.github/workflows/release.yml`.
 
-The workflow runs on pushes to `main`. It expects a repository secret named
-`RELEASE_PLEASE_GITHUB_TOKEN`.
+The workflow runs on pushes to `main`. It uses the `RELEASE_PLEASE_GITHUB_TOKEN` repository secret
+when configured and falls back to the workflow `GITHUB_TOKEN` otherwise.
 
 ## Token
 
@@ -38,6 +38,10 @@ gh secret set RELEASE_PLEASE_GITHUB_TOKEN --repo bullets-vim/bullets.nvim
 
 Paste the token when prompted.
 
+Without this secret, release-please can still run with `GITHUB_TOKEN`, but release PRs and tags created by
+`GITHUB_TOKEN` will not trigger follow-up workflow runs. Use the fine-grained token when release-please PRs
+need normal CI checks.
+
 ## Release Flow
 
 1. Merge conventional commits to `main`.