Delete add-parent-context-flag.sh

[JakeSCahill]

Description

Resolves https://redpandadata.atlassian.net/browse/
Review deadline:

Page previews

Checks

• New feature
• Content gap
• Support Follow-up
• Small fix (typos, links, copyedits, etc)

[netlify]

✅ Deploy Preview for redpanda-docs-preview ready!

Name	Link
🔨 Latest commit	7648620
🔍 Latest deploy log	https://app.netlify.com/projects/redpanda-docs-preview/deploys/6a27d55f7d82f7000828dc2e
😎 Deploy Preview	https://deploy-preview-1732--redpanda-docs-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1b800599-d83a-47ce-a8a2-230013eefd3a

📥 Commits

Reviewing files that changed from the base of the PR and between 0a37226 and 7648620.

📒 Files selected for processing (1)

• add-parent-context-flag.sh

💤 Files with no reviewable changes (1)

• add-parent-context-flag.sh

---

📝 Walkthrough

Walkthrough

This PR removes the add-parent-context-flag.sh bash script. The script previously iterated over hardcoded feature branches, checked and updated antora.yml files to add a page-use-parent-context: true flag when missing using sed, committed those changes, and provided push instructions. The script is no longer needed and has been deleted.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• paulohtb6

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description uses the required template structure but contains unfilled placeholders and no checked items, leaving critical details unspecified.	Complete the Jira ticket link, add a review deadline if needed, and select the appropriate check (likely 'Small fix' for script removal).

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Delete add-parent-context-flag.sh' accurately and specifically describes the main change—the removal of the script file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch JakeSCahill-patch-5

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Feediver1]

One interesting observation (not blocking)

The script's intended effect — adding page-use-parent-context: true to antora.yml — is not present on any
current branch. I checked main and all 7 maintained v/* branches: none has the flag.

So either (a) the script was run, the rename PRs that DID merge dropped the flag in their final form, and the
parent-context-navigation feature was tabled; or (b) the script was never executed.

Not a blocker — just worth noting that deleting the script also removes the recipe for re-enabling this flag if
anyone wants to revisit the feature later. If that history is worth preserving, a one-line commit message
describing what the flag does would help; if not, deletion is fine.

What this PR doesn't do

• Doesn't touch any documentation content.
• Doesn't enable or disable any rendered behavior on the docs site.
• Doesn't affect builds (Netlify preview is green).

Recommendation

Approve as-is. It's a pure repo-tidiness deletion of a script whose purpose has been fulfilled or abandoned. If
you want the recipe preserved, mention the script in a CHANGELOG / commit body — but the change itself is
safe.