Repository navigation
Update CodeBoarding workflow configuration - #3
Conversation
CodeBoarding reviewStatus: 0 changed components (no analysed file changed) See the full change in CodeBoarding. graph LR
n_Coding_Agent_Application["Coding Agent Application"]
n_AI_Model_Providers_and_Runtime["AI Model Providers and Runtime"]
n_Durable_Execution_Engine["Durable Execution Engine"]
n_Protocol_and_Service_Mesh["Protocol and Service Mesh"]
n_Terminal_User_Interface_Framework["Terminal User Interface Framework"]
n_Build_and_Maintenance_Scripts["Build and Maintenance Scripts"]
n_Model_Context_Protocol_Client["Model Context Protocol Client"]
n_Codemode_Sandbox_Runtime["Codemode Sandbox Runtime"]
n_Telemetry_Instrumentation["Telemetry Instrumentation"]
n_Coding_Agent_Application -- "queries models and configures agent execution v…" --> n_AI_Model_Providers_and_Runtime
n_Coding_Agent_Application -- "renders terminal interface with" --> n_Terminal_User_Interface_Framework
n_Coding_Agent_Application -- "configures workflows and extensions in" --> n_Durable_Execution_Engine
n_Coding_Agent_Application -- "establishes connections and binds services via" --> n_Protocol_and_Service_Mesh
n_Coding_Agent_Application -- "authorizes and communicates through" --> n_Model_Context_Protocol_Client
n_Coding_Agent_Application -- "executes sandboxed code via" --> n_Codemode_Sandbox_Runtime
n_AI_Model_Providers_and_Runtime -- "prompts user login via" --> n_Coding_Agent_Application
n_Durable_Execution_Engine -- "invokes model runtime completions in" --> n_Coding_Agent_Application
n_Durable_Execution_Engine -- "queries model configurations from" --> n_AI_Model_Providers_and_Runtime
n_Durable_Execution_Engine -- "utilizes context and serialization utilities fr…" --> n_Protocol_and_Service_Mesh
n_Protocol_and_Service_Mesh -- "hosts and manages services defined in" --> n_Coding_Agent_Application
n_Protocol_and_Service_Mesh -- "replicates committed state from" --> n_Durable_Execution_Engine
n_Terminal_User_Interface_Framework -- "triggers user interface rendering in" --> n_Coding_Agent_Application
n_Build_and_Maintenance_Scripts -- "verifies and generates catalog definitions from" --> n_AI_Model_Providers_and_Runtime
n_Build_and_Maintenance_Scripts -- "invokes session and storage utilities in" --> n_Coding_Agent_Application
n_Build_and_Maintenance_Scripts -- "manages session documents via" --> n_Durable_Execution_Engine
n_Model_Context_Protocol_Client -- "persists OAuth credentials via" --> n_Coding_Agent_Application
n_Codemode_Sandbox_Runtime -- "calls back into tool execution in" --> n_Coding_Agent_Application
classDef added fill:#1f883d,stroke:#0b5d23,color:#ffffff;
classDef modified fill:#bf8700,stroke:#7d4e00,color:#ffffff;
classDef deleted fill:#cf222e,stroke:#82071e,color:#ffffff,stroke-dasharray:5 3;
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 66f6d8a6a0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - uses: CodeBoarding/CodeBoarding-action@v1 | ||
| with: | ||
| mode: sync |
There was a problem hiding this comment.
@v1 defaults sync_strategy to push and target_branch to the event branch, as shown in its input contract; for this push-triggered job that branch is main. The sync therefore recreates the deleted .codeboarding/* state on main, contrary to the workflow comment and commit description claiming it is stored on codeboarding/baseline. Configure a supported separate delivery topology or retain the baseline and generated-file path filters on main.
Useful? React with 👍 / 👎.
| # Sync keeps one branch's analysis, so this lists exactly one. There is no manual | ||
| # trigger: a dispatch could run sync on any branch. |
There was a problem hiding this comment.
Removing workflow_dispatch also removes the only path that passed force_full, so maintainers cannot explicitly rebuild a compatible but stale or incorrect baseline without changing repository state or editing the workflow. Guard the dispatch to main or set an explicit target instead of deleting this recovery control without confirmation.
AGENTS.md reference: AGENTS.md:L23-L26
Useful? React with 👍 / 👎.
1 participant
Preview first, merge when ready
View your map · Configure & merge
The preview runs on this pull request. Merge the workflow to keep maps updated. Settings can be changed in this same pull request before merging.
This PR brings your CodeBoarding setup to the current shape:
one workflow file,
codeboarding.yml, with a review and a sync job. It regeneratesthat file so it will:
llm: hosted, which needsno secret at all, and
id-token: write, which is how a run identifies your repository to the hostedtier. Nothing else to configure.
Sync delivery
Sync saves the generated diagram on its own
codeboarding/baselinebranch in this repository;mainnever changes and there is nothing to merge.Cleaned up
.codeboarding/frommain(5). The analysis now lives oncodeboarding/baseline, so a copy here would only go stale. Your configuration (.codeboardingignore, the health settings) stays.Only CodeBoarding’s own files are touched. If you’d customized a workflow, review the
diff before merging.
Opened for you by CodeBoarding.