You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* fix: install CodeBoarding engine from PyPI
Amp-Thread-ID: https://ampcode.com/threads/T-019edcb0-130a-713d-8e97-997ec5e29b33
Co-authored-by: Amp <amp@ampcode.com>
* fix: pin engine to codeboarding 0.12.3 and use Python 3.12
Bump the codeboarding_version default to 0.12.3 (latest published) across
action.yml and the README.
Also switch the action's setup-python from 3.13 to 3.12: the codeboarding
package's transitive dep langchain-cerebras (>=0.8) is published only for
>=3.11,<3.13, so a 3.13 runner cannot resolve the engine install (true for
both 0.12.2 and 0.12.3). Verified 0.12.3 installs cleanly on 3.12 and the
codeboarding-setup entry point is present.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* fix: check out PR head for /codeboarding (issue_comment) runs
The review workflow dogfoods via `uses: ./`, but on issue_comment events
actions/checkout defaults to the repo's default branch (the event isn't tied
to a PR), so /codeboarding ran main's action code instead of the PR's. Pass an
explicit ref (refs/pull/<n>/head) for issue_comment so the comment path
exercises the PR under review too; pull_request events keep checkout's default
(the PR merge ref), so they are unchanged.
Takes effect once on main, since GitHub reads the issue_comment workflow
definition from the default branch.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Amp <amp@ampcode.com>
Co-authored-by: Svilen Stefanov <svilen.ks@gmail.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -264,7 +264,7 @@ Review mode does not need `contents: write`: PR-specific generated files are sto
264
264
|`mode`| both |`review`|`review` posts the PR architecture-diff comment; `sync` analyzes on push and commits the architecture (`analysis.json` + rendered docs) to `target_branch`, keeping it versioned and current. |
265
265
|`github_token`| both |`${{ github.token }}`| Token for GitHub API calls; in review mode it posts or updates the PR comment. |
266
266
|`push_token`| sync |`${{ github.token }}`| Token used for sync-mode pushes to `target_branch`. The workflow token can push when the workflow grants `permissions: contents: write`. Separate from `github_token` so commenting can use a GitHub App token while the push uses the workflow token. |
267
-
|`engine_ref`| both |`v0.12.1`| CodeBoarding engine ref. Pin for reproducibility. |
267
+
|`codeboarding_version`| both |`0.12.3`| CodeBoarding PyPI package version used as the analysis engine. Pin for reproducibility. |
268
268
|`depth_level`| both | empty (`2` for cold starts) | Analysis depth, 1 to 3, used for first analysis and `force_full` rebuilds. Once `.codeboarding/analysis.json` exists, its `metadata.depth_level` is the source of truth for incremental analysis and fallback-full recovery. |
269
269
|`render_depth`| review |`1`| Display depth for the PR diagram. Keep `1` for a clean top-level view. |
@@ -298,7 +298,7 @@ Outputs of the mode that did not run are empty strings.
298
298
299
299
## Notes
300
300
301
-
- No checkout step is required in your workflow. This action checks out the target (the PR in review mode, the pushed commit in sync mode) and the CodeBoarding engine internally.
301
+
- No checkout step is required in your workflow. This action checks out the target (the PR in review mode, the pushed commit in sync mode) and installs the CodeBoarding engine from PyPI internally.
302
302
- GitHub withholds secrets from fork PRs on `pull_request`, so fork runs fail early if an LLM key is unavailable.
303
303
- Do not use `pull_request_target` for this action. It can expose secrets to PR-head code.
304
304
- GitHub renders Mermaid in strict mode, so node click-through links are not supported in the PR diagram.
Copy file name to clipboardExpand all lines: action.yml
+37-63Lines changed: 37 additions & 63 deletions
Original file line number
Diff line number
Diff line change
@@ -31,10 +31,10 @@ inputs:
31
31
description: 'Token used for sync-mode git pushes to target_branch. Defaults to the workflow github.token, which can push when the calling workflow grants "permissions: contents: write". Kept separate from github_token so commenting can use a GitHub App token while the push uses the workflow token (whose write access the consumer controls).'
32
32
required: false
33
33
default: ${{ github.token }}
34
-
engine_ref:
35
-
description: 'Git ref (tag/branch/SHA) of CodeBoarding/CodeBoarding used as the analysis engine. Pinned to a release for reproducibility; override to track a newer ref.'
34
+
codeboarding_version:
35
+
description: 'CodeBoarding PyPI package version used as the analysis engine. Pin for reproducibility; set to a newer released version to opt into newer engine releases.'
36
36
required: false
37
-
default: 'v0.12.1'
37
+
default: '0.12.3'
38
38
depth_level:
39
39
description: 'Analysis depth (1-3) for cold-start or force_full rebuilds. Once .codeboarding/analysis.json exists, its metadata.depth_level is the source of truth for incremental analysis and fallback-full recovery. Empty (default): 2 for cold starts.'
40
40
required: false
@@ -142,7 +142,7 @@ runs:
142
142
# interleave only because they share the LLM-key lifecycle, NOT because they
0 commit comments