Repository navigation
Update CodeBoarding workflow configuration - #4
ivanmilevtues wants to merge 1 commit into
Conversation
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. |
CodeBoarding review · failedThe LLM provider's token or credit quota is exhausted. Add credits or raise the quota, then re-run. See the workflow logs. |
![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: dd6e6aac5c
ℹ️ 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".
This branch has not been deployed
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.Protect
codeboarding/baselineSync and review load a Python pickle from that branch, and loading a pickle runs code, so anyone
who can push to it can run code in these workflows. Import a ruleset under Settings, Rules,
Rulesets, New ruleset, Import a ruleset, before the first sync:
baseline-branch-ruleset-actions.jsonfits this workflowas generated, which pushes with the default
github.token. It stops people pushing by hand,but any workflow with
contents: writecan still write the branch.baseline-branch-ruleset.jsonlets only the CodeBoarding Review appwrite it. Use it when sync pushes with the app's token as
github_token.More in the baseline branch. Rulesets on a private
repository need a paid GitHub plan.
Only CodeBoarding’s own files are touched. If you’d customized a workflow, review the
diff before merging.
Opened for you by CodeBoarding.