Skip to content

chore(sync): merge sync/auto/main-20260408-154438 into main#12

Open
Articrafter93 wants to merge 1 commit into
mainfrom
sync/auto/main-20260408-154438
Open

chore(sync): merge sync/auto/main-20260408-154438 into main#12
Articrafter93 wants to merge 1 commit into
mainfrom
sync/auto/main-20260408-154438

Conversation

@Articrafter93

Copy link
Copy Markdown
Owner

Automated indirect sync from protected branch via gh skill.

@Articrafter93 Articrafter93 enabled auto-merge (squash) April 8, 2026 20:44

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

Copy link
Copy Markdown

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: c1b7f445e5

ℹ️ 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 thread vercel.json
"buildCommand": "npm run build",
"outputDirectory": ".next"
"outputDirectory": ".next",
"ignoreCommand": "if [ -n \"${VERCEL_GIT_COMMIT_SHA:-}\" ] || [ -n \"${VERCEL_GIT_COMMIT_REF:-}\" ]; then echo \"Skipping Git-triggered deployment. revision-final plus manual release is required.\"; exit 0; fi; exit 1"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Avoid consuming deployment quota with blanket ignoreCommand

This ignoreCommand returns 0 whenever Git commit metadata is present, so every Git-triggered deployment is canceled. In Vercel's Ignored Build Step behavior, exit 0 cancels the build and canceled builds still count toward deployment quotas and concurrent build slots, so normal branch activity can burn capacity without producing a deployable build. If your release path depends on manual promotion or redeploy, this can block releases after enough commits.

Useful? React with 👍 / 👎.

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