Skip to content

feat: add force push to CLI#1359

Open
cjbell wants to merge 1 commit intomainfrom
cb-force-push
Open

feat: add force push to CLI#1359
cjbell wants to merge 1 commit intomainfrom
cb-force-push

Conversation

@cjbell
Copy link
Contributor

@cjbell cjbell commented Mar 18, 2026

Description

  • Adds new --force guidance to pushing resources
  • Adds missing audiences section for the CLI ref

@vercel
Copy link

vercel bot commented Mar 18, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Mar 18, 2026 7:24pm

Request Review

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Risk MEDIUM: Adds --force flag documentation to CLI push commands across multiple resources and introduces a new audiences CLI reference page with sidebar navigation changes.

Reasons

  1. A new MDX page is added (content/cli/audience.mdx with 342 lines), which introduces a new documentation page that needs review for accuracy and consistency with existing CLI reference pages.
  2. The sidebar navigation file (data/sidebars/cliSidebar.ts) is modified to add the new audiences section, which affects site navigation.
  3. Changes span three documentation sections (content/cli/, content/developer-tools/, and content/version-control/), increasing the surface area for potential inconsistencies.
  4. The diff is substantial at 402 additions across 11 files, above the typical LOW-risk threshold.
  5. No HIGH-risk triggers are present — no component, layout, build config, or dependency changes.

Notes

  • Verify the new content/cli/audience.mdx page renders correctly and all internal links (e.g., /cli/audience/file-structure, /cli/audience/push) resolve properly given the single-file section-based structure.
  • Confirm the --force flag descriptions are consistent across all resource push commands (workflow, partial, guide, message-type, email-layout, translation, resources, and audience).
  • Check that the sidebar entry for audiences appears in the correct position and that all slug paths match the section anchors in audience.mdx.
  • Review the new paragraph in content/developer-tools/integrating-into-cicd.mdx about --force as an alternative to the push/commit/promote workflow — ensure the messaging around bypassing environment restrictions is appropriately cautious.
Open in Web View Automation 

Sent by Cursor Automation: Docs PR classifier

Copy link
Contributor

@rachael-t rachael-t left a comment

Choose a reason for hiding this comment

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

🎉

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.

2 participants