Claude
625a130366
Opening this pull request through the API produced no workflow run, so the previous version of this file was wrong about the API route being the fix. The suppression covers everything the sandbox does — pushes, pull request opens, and merges — because it follows the integration, not the account the UI attributes the action to. workflow_dispatch is the only mechanism that works, because it creates a run directly rather than relying on an event. Record the loop that follows from that, including the part worth having: ci.yml gates only its staging and publishing steps on refs/heads/dev, so dispatching it on a feature branch runs build, tests and lint while publishing nothing. That is a real pre-merge gate with no YAML changes. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01YEsqYAMJKUJoM7UAavm169
70 lines
2.9 KiB
Markdown
70 lines
2.9 KiB
Markdown
# Working on this repo with Claude
|
|
|
|
## Nothing a session does triggers CI. Dispatch it explicitly.
|
|
|
|
GitHub creates **no workflow run** for anything this sandbox does — pushing a
|
|
branch, opening a pull request, or merging one. All of it goes through the same
|
|
integration, and GitHub suppresses event-triggered runs from it. The pull
|
|
request will say it was opened by the repo owner; that is only how the UI
|
|
attributes it, and it does not change the suppression.
|
|
|
|
This was measured, not assumed:
|
|
|
|
| Action | Result |
|
|
| --- | --- |
|
|
| Human pushes a Claude-authored commit (`d165e5ef`, `469c900e`) | CI runs |
|
|
| Session pushes `dev` / `main` (`43394b8`, `742add4`) | no run |
|
|
| Session opens a PR against `dev` (#1) | no run |
|
|
| Session calls `workflow_dispatch` | **runs** |
|
|
|
|
`workflow_dispatch` works because it creates a run directly instead of relying
|
|
on an event. It is the only mechanism available from a session, so every build
|
|
has to be asked for by hand.
|
|
|
|
## Verify before merging, without publishing
|
|
|
|
`ci.yml` builds, tests and lints on any ref, but its staging and publishing
|
|
steps are gated on `github.ref == 'refs/heads/dev'`. Dispatching it on a
|
|
**feature branch** therefore gives the full check — build, unit tests, Android
|
|
lint — and publishes nothing.
|
|
|
|
So the working loop is:
|
|
|
|
1. Commit and push the feature branch.
|
|
2. Dispatch `ci.yml` on that branch. Wait for green. This is the real review
|
|
gate, and it is the only verification that exists (see below).
|
|
3. Open the PR through the API and merge it there, so the change is reviewable
|
|
and the merge commit is honest about what happened. Neither step builds
|
|
anything.
|
|
4. Dispatch the target branch's workflow to actually build and publish:
|
|
`ci.yml` on `dev`, `release.yml` on `main`.
|
|
|
|
Skipping step 4 leaves a branch whose head was never built and no release.
|
|
|
|
## Merging is a shipping action
|
|
|
|
Both long-lived branches publish, so a merge is a release, not just an
|
|
integration:
|
|
|
|
- **`dev`** → `ci.yml` publishes a `v1.0.N-dev` **prerelease**, offered by the
|
|
in-app updater to anyone on the Dev channel.
|
|
- **`main`** → `release.yml` publishes a **production** release, which the
|
|
updater installs for everyone on the Production channel.
|
|
|
|
Confirm before shipping to `main`. Note that `release.yml` runs `assembleDebug`
|
|
only — no tests, no lint — so a `main` release is only as verified as the `dev`
|
|
build it replays.
|
|
|
|
## Gradle does not run in the sandbox
|
|
|
|
`./gradlew` cannot resolve the Android plugin here: the proxy blocks
|
|
`dl.google.com` with a 403. No local build, no local test run, no local lint. A
|
|
dispatched CI run is the only way to find out whether a change compiles.
|
|
|
|
## A permanent fix, if you want one
|
|
|
|
The suppression is a property of the sandbox's credential, so it cannot be
|
|
fixed from inside a session. Giving the environment a personal access token to
|
|
push with would make pushes and PRs behave normally for everyone. Until then,
|
|
the dispatch step above is the workaround.
|