Skip to content

Comments

DRAFT: Submission bot opens a github PR #4044

Draft
tintinthong wants to merge 2 commits intoget-bot-runner-to-run-headless-commandfrom
cs-9945-submission-bot-open-a-github-pr
Draft

DRAFT: Submission bot opens a github PR #4044
tintinthong wants to merge 2 commits intoget-bot-runner-to-run-headless-commandfrom
cs-9945-submission-bot-open-a-github-pr

Conversation

@tintinthong
Copy link
Contributor

No description provided.

@tintinthong tintinthong changed the base branch from main to get-bot-runner-to-run-headless-command February 23, 2026 14:47
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 935b2c0665

ℹ️ 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".

Comment on lines +65 to +68
let prParams: Parameters<CreatePullRequest>[0] = {
...params,
head: HARDCODED_PR_HEAD_BRANCH,
};

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Respect caller-provided PR head branch

openPullRequest currently replaces params.head with a hardcoded branch, so every PR is opened from test-submissions regardless of the event/listing-specific branch passed by callers. This breaks branch isolation and can open the wrong PR (or fail if that branch is absent), which makes the submission flow unreliable for any room-specific listing updates.

Useful? React with 👍 / 👎.

Comment on lines +169 to +172
if (eventContent.type === 'pr-listing-create') {
// Temporary workaround: handle PR creation directly until this flow is moved to a proper command path.
await openCreateListingPR({
eventContent,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Return after direct pr-listing-create handling

For pr-listing-create, this function calls openCreateListingPR but then continues into the generic enqueue path instead of exiting, so the same trigger can both open a PR directly and enqueue a run-command job. In environments where that event type has an allowed command registration, this causes duplicated/competing side effects for a single Matrix event.

Useful? React with 👍 / 👎.

@tintinthong tintinthong marked this pull request as draft February 23, 2026 14:52
@github-actions
Copy link

Preview deployments

@github-actions
Copy link

github-actions bot commented Feb 23, 2026

Host Test Results

    1 files  ±0      1 suites  ±0   1h 38m 42s ⏱️ +30s
1 856 tests +2  1 842 ✅ +2  14 💤 ±0  0 ❌ ±0 
1 871 runs  +2  1 857 ✅ +2  14 💤 ±0  0 ❌ ±0 

Results for commit d54d5fc. ± Comparison against base commit 751930f.

♻️ This comment has been updated with latest results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant