Skip to content

Add CodeBoarding architecture analysis - #1

Merged
ivanmilevtues merged 2 commits into
devfrom
codeboarding/setup-action
Sep 24, 2026
Merged

ivanmilevtues merged 2 commits into
devfrom
codeboarding/setup-action

Conversation

@ivanmilevtues

@ivanmilevtues ivanmilevtues commented Sep 24, 2026 •

Copy link
Copy Markdown
Member

Preview first, merge when ready

View your map · Configure & merge

The preview runs on this pull request. Merge the workflows to keep maps updated. Settings can be changed in this same pull request before merging.

This PR adds the CodeBoarding GitHub Action via two workflows:

  • codeboarding-sync.yml: on every push to dev, commits
    .codeboarding/analysis.json (your architecture baseline + readable docs). This is
    what the CodeBoarding viewer opens.
  • codeboarding.yml: runs on every push to a pull request, keeping an
    architecture-diff comment current and uploading that PR’s analysis as a build artifact
    for the viewer’s PR diff. Each run continues from the one before it, so a push costs a
    fraction of a full analysis.

Both are needed: sync produces the baseline; review diffs against it.

Sync delivery

Sync commits the generated baseline directly to dev.

Works out of the box

Just merge it: the Action runs on the free tier, with no secret to add. The
id-token: write permission lets it identify your repo to CodeBoarding’s hosted LLM,
metered against a weekly limit for the repository owner.

Want more, or unmetered, usage?

Switching is a change to these workflow files rather than a secret you add, because the
file names which credentials a run uses. Use Configure & merge in the viewer to pick:

  • a CodeBoarding plan (unmetered, and raises the analysis-depth ceiling from 3 to 10), or
  • your own provider key: OpenRouter, Anthropic, OpenAI, Google, AWS Bedrock and
    others.

Before merging, this updates the same setup pull request and tells you which secret to
add under Settings → Secrets and variables → Actions.
After merging, use repository settings in the dashboard to open an update PR.

Opened for you by CodeBoarding.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-24T23:52:56.806939Z a14bf30 PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@github-actions

Copy link
Copy Markdown

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

  • PR description is missing required template sections. Please use the PR template.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

@github-actions

Copy link
Copy Markdown

Hey! Your PR title Add CodeBoarding architecture analysis doesn't follow conventional commit format.

Please update it to start with one of:

  • feat: or feat(scope): new feature
  • fix: or fix(scope): bug fix
  • docs: or docs(scope): documentation changes
  • chore: or chore(scope): maintenance tasks
  • refactor: or refactor(scope): code refactoring
  • test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

1 similar comment
@github-actions

Copy link
Copy Markdown

Hey! Your PR title Add CodeBoarding architecture analysis doesn't follow conventional commit format.

Please update it to start with one of:

  • feat: or feat(scope): new feature
  • fix: or fix(scope): bug fix
  • docs: or docs(scope): documentation changes
  • chore: or chore(scope): maintenance tasks
  • refactor: or refactor(scope): code refactoring
  • test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

@github-actions

Copy link
Copy Markdown

CodeBoarding review · analyzing…

⏳ CodeBoarding is analyzing this pull request's architecture changes.

run 36074819292 · attempt 1

@ivanmilevtues
ivanmilevtues merged commit fec64ac into dev Sep 24, 2026
5 of 13 checks passed
@ivanmilevtues
ivanmilevtues deleted the codeboarding/setup-action branch September 24, 2026 23:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant