standup-mr 0.1.2 → 0.2.1

package/CHANGELOG.md

@@ -0,0 +1,94 @@
+# Changelog
+
+All notable changes to standup-mr are recorded here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the project uses
+[semantic versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.2.1] - 2026-08-31
+
+### Fixed
+
+- A pull request whose CI timed out was reported as ready to merge. GitHub
+  reports a timed-out job with the conclusion `cancelled`, not `timed_out`, so
+  it normalised to a `canceled` pipeline — and a canceled pipeline was treated
+  as a green light. A canceled pipeline now blocks, on both providers: GitLab's
+  `canceled` status took the same path.
+- Every error line in a GitHub blocker was reported twice. GitHub Actions echoes
+  a step's script inside a `##[group]Run …` block before running it, and those
+  echoed lines matched the error patterns. The body of a `Run` group is now
+  suppressed; other groups are still scanned, since they carry real output.
+
+Both were found by testing 0.2.0 against the real GitHub Actions API — neither
+was reachable from the test fixtures.
+
+## [0.2.0] - 2026-08-31
+
+GitHub joins GitLab as a first-class provider, and the previous-day report
+stops throwing work away. Both changes break existing shapes — read the
+migration notes before upgrading.
+
+### Added
+
+- **GitHub provider.** Pull requests, review requests, activity events, and
+  blockers, on `github.com` and on GitHub Enterprise (`/api/v3`). When CI is
+  red the failed Actions job's log is opened and its error lines reported, with
+  a fall back to a non-Actions check run's summary.
+- **Provider selection.** `--provider github` / `--provider gitlab`, the
+  `STANDUP_PROVIDER` environment variable, host-name recognition, and a fall
+  back to whichever of `gh` / `glab` is logged in. Ambiguity fails with a clear
+  error rather than a guess.
+- `provider` on the report and on every merge request, review, and blocker, so
+  a consumer can pick the right vocabulary (`!123` vs `#123`).
+
+### Changed
+
+- **BREAKING — JSON output: `previous` and `previousEvents` are gone,**
+  replaced by `previousDays[]`. Each entry carries `date`, `label`, `gapDays`,
+  and its own `events`. The old single-day shape reported only the most recent
+  active day, so a Saturday with any activity at all silently discarded the
+  whole of Friday's work — which is exactly the day a Monday standup is about.
+  Anyone piping `standup fetch | jq .previous` now gets `null` with no error;
+  read `.previousDays` instead, and write up every entry.
+- **BREAKING — library API:**
+  - `Provider.getReviews(identity, today)` takes an `Identity` object where it
+    previously took a numeric user id. GitHub searches by login, GitLab by
+    numeric id, so the contract has to carry both.
+  - `MergeRequest`, `Review` and `Blocker` each gained a **required**
+    `provider` field.
+  - `getJson` now **throws** an `ApiError` on an authentication or rate-limit
+    failure where it previously returned `null`. `null` is reserved for exactly
+    one case: a 404. Previously an invalid token produced an empty standup note
+    that looked like a quiet day.
+- **BREAKING — MCP:** `CollectOptions.provider` changed meaning. It is now a
+  provider *name* (`'github'` / `'gitlab'`); the injection point for a
+  `Provider` instance is the new `CollectOptions.providerImpl`.
+- The `standup` skill (`skills/standup/SKILL.md`) changed incompatibly with
+  0.1.x: it reads `previousDays` and carries provider-specific vocabulary
+  rules. Run `/plugin marketplace update standup-mr` after upgrading.
+
+### Fixed
+
+- A red pipeline whose Actions run or job **timed out** (or hit
+  `startup_failure` / `action_required`) now reaches the job log instead of
+  degrading silently to the check-run summary.
+- An Actions blocker with no error lines no longer suppresses the check-run
+  fallback that held the real reason.
+- GitHub's **secondary** rate limit (403 with `retry-after` and a non-zero
+  remaining count) is reported as a rate limit with the retry delay, not as a
+  missing-permissions error.
+- An ambient `GITHUB_TOKEN` — exported by dotfiles and CI everywhere — no
+  longer hard-errors a working GitLab setup. When both environment pairs are
+  present, the pair that names a `*_HOST` wins.
+- `getEvents` stops paging at GitHub's documented ~300-event feed cap instead
+  of requesting a page beyond it.
+- An unreachable job log degrades to "no error lines" rather than failing the
+  whole run.
+
+## [0.1.2] - 2026-08-28
+
+- Initial published line: GitLab merge requests, buckets, review queue, and
+  failed-pipeline diagnosis from the job trace. CLI, MCP server, and Claude
+  Code skill.
+
+[0.2.0]: https://github.com/Jubstaaa/standup-mr/releases/tag/v0.2.0
+[0.1.2]: https://github.com/Jubstaaa/standup-mr/releases/tag/v0.1.2

package/README.md

@@ -3,35 +3,55 @@
 Standup notes from **merge request state**, not commit logs.
 
 Most standup tools read your local `git log`. That answers "what did I type",
-which is not what anyone asks in a standup. This one reads GitLab: what is ready
-to merge, what is blocked, what is waiting on you — and when a pipeline is red,
-it opens the job log and tells you **why**.
+which is not what anyone asks in a standup. This one reads GitLab or GitHub:
+what is ready to merge, what is blocked, what is waiting on you — and when a
+pipeline is red, it opens the job log and tells you **why**.
 
 ## What makes it different
 
 |  | commit-log tools | standup-mr |
 |---|---|---|
-| Source | local `git log` | GitLab API |
+| Source | local `git log` | GitLab or GitHub API |
 | Merge request state | ✗ | ready / blocked / draft / stale |
 | Review queue | ✗ | pending only, approvals filtered out |
-| Failed pipeline | ✗ | error lines pulled from the job trace |
-| Self-hosted GitLab | varies | first class |
+| Failed pipeline | ✗ | error lines from the job trace or the Actions job log |
+| Self-hosted (GitLab CE/EE, GitHub Enterprise) | varies | first class |
 
 ## Use
 
 ```bash
-npx standup-mr fetch                 # JSON
-npx standup-mr fetch --markdown      # structured digest
-npx standup-mr fetch --lang tr       # Turkish date labels
+npx standup-mr fetch                            # JSON, provider auto-detected
+npx standup-mr fetch --provider github          # GitHub
+npx standup-mr fetch --provider gitlab          # GitLab
+npx standup-mr fetch --markdown                 # structured digest
+npx standup-mr fetch --lang tr                  # Turkish date labels
 ```
 
-Credentials resolve in this order, independently for host and token:
+### Identity
 
-1. `--host` / `--token`
-2. `GITLAB_HOST` / `GITLAB_TOKEN`
-3. the local [`glab`](https://gitlab.com/gitlab-org/cli) CLI config
+| | GitHub | GitLab |
+|---|---|---|
+| Flags | `--host` / `--token` | `--host` / `--token` |
+| Env | `GITHUB_HOST` / `GITHUB_TOKEN` | `GITLAB_HOST` / `GITLAB_TOKEN` |
+| CLI session | [`gh`](https://cli.github.com/) auth config | [`glab`](https://gitlab.com/gitlab-org/cli) auth config |
+
+GitHub defaults to `github.com` when no host is given. GitLab has no default —
+self-hosted is the norm there, so a host must come from a flag, env var, or
+`glab`'s own config.
+
+The provider itself is picked in this order:
+
+1. `--provider github` / `--provider gitlab`, if passed
+2. a recognizable `--host` (`github.com`, `gitlab.com`, or a hostname
+   containing `github`/`gitlab`)
+3. `STANDUP_PROVIDER`, or whichever of the `GITHUB_*` / `GITLAB_*` env pairs
+   is set
+4. whichever of `gh` / `glab` is logged in
 
-So if you already use `glab`, there is nothing to configure.
+If none of these resolve — or both do, ambiguously — the command fails with a
+clear error instead of guessing.
+
+So if you already use `gh` or `glab`, there is nothing to configure.
 
 ### Post it to chat
 
@@ -46,21 +66,15 @@ npx standup-mr fetch --markdown | npx standup-mr post --slack "$SLACK_WEBHOOK_UR
 **MCP server** (`mcp/`) — one tool, `get_standup_data`, for Claude Desktop,
 Cursor, or any MCP client. See [`mcp/README.md`](mcp/README.md).
 
-**Claude Code skill** (`skills/standup/`) — the note-writing playbook. Install
-it as a plugin from inside Claude Code:
+**Claude Code plugin** — the note-writing playbook, shipped as the `standup`
+skill. From inside Claude Code:
 
 ```
 /plugin marketplace add Jubstaaa/standup-mr
 /plugin install standup@standup-mr
 ```
 
-Then type `/standup`.
-
-Or, without the plugin marketplace, copy it in manually:
-
-```bash
-cp -r skills/standup ~/.claude/skills/standup
-```
+Then type `/standup`. Updates come with `/plugin marketplace update standup-mr`.
 
 ## `--markdown` is a digest, not a written note
 
@@ -71,6 +85,81 @@ lives in the MCP client's prompt or in the Claude Code skill.
 - Without AI: a structured digest.
 - With AI: a note you can read out.
 
+## What the digest looks like
+
+Anonymised output from a real Monday run — note that Friday and Saturday each
+get their own section, and that a merge request GitLab has not evaluated is not
+called ready:
+
+```markdown
+# Monday, 31 August — dev
+
+_Structured digest — not a written note._
+
+## Previous working day: Friday, 28 August
+
+- `acme/ui` pushed to — fix(keyboard): scale keys to viewport (4 commits)
+- `acme/ui` accepted — chore(deps): bump @acme/ui to 0.5.18
+- `acme/api` opened — feat: package subscription sales
+
+## Previous working day: Saturday, 29 August
+
+- `acme/ui` pushed to — fix(keyboard): close the autofill bar (1 commit)
+
+## Ready to merge (2)
+
+- `acme/api` !196 fix: normalise the +90 trunk prefix
+- `acme/web` !194 refactor: loading state — **no pipeline ran**
+
+## Blocked (1)
+
+- `acme/terminal` !49 fix: relative date chips — **1 unresolved comment(s)**
+
+## Reviews (2 pending)
+
+- `acme/mobile` !501 chore: upgrade to RN 0.87 — Teammate
+
+## Blockers
+
+- `acme/mobile` !6 — job `quality`
+  - `npm ERR! code E404`
+  - `npm ERR! 404 Not Found - GET https://registry.example.com/@acme%2fui`
+```
+
+The last section is the point of the tool. Every other standup tool can tell you
+that pipeline is red; this one opens the failed job's log and shows you the
+404 — and a 404 rather than a 403 usually means the token's scope is wrong, not
+that the package is missing.
+
+## Known limits
+
+- **GitHub's events feed is shallow.** It is capped at roughly 300 events over
+  the last 90 days, so a very active account or an old gap can silently lose
+  the earliest events. GitLab has no comparable documented cap.
+- **GitHub activity is only visible to a token belonging to that same
+  account**, and private-repository events do not show up for anyone else's
+  token, even with otherwise sufficient scopes.
+- **On GitHub, CI that reports only through the legacy commit-statuses API**
+  — still how some vendors integrate — shows up as `pipelineMissing`. Check
+  state is read from check-runs only.
+
+## Upgrading from 0.1.x
+
+0.2.0 changes the JSON output, the library API, and the MCP options. If you
+pipe `standup fetch` into anything, or import the package, read
+[`CHANGELOG.md`](CHANGELOG.md) before upgrading. The short version:
+
+- `previous` and `previousEvents` are replaced by `previousDays[]`, one entry
+  per active day, so a weekend no longer swallows Friday. `jq .previous` now
+  returns `null` with no error.
+- `MergeRequest`, `Review` and `Blocker` carry a required `provider` field, and
+  `Provider.getReviews` takes an `Identity` rather than a numeric id.
+- The MCP `CollectOptions.provider` is now a provider *name*; inject a
+  `Provider` instance through `providerImpl`.
+
+Claude Code plugin users should run `/plugin marketplace update standup-mr` —
+the `standup` skill changed along with the report shape.
+
 ## Requirements
 
 Node 20 or newer. No runtime dependencies.