Skip to content

Remove green elephant markers from what-is-baml headings - #4598

Draft
ATX24 wants to merge 1 commit into
canaryfrom
cursor/remove-green-elephant-markers-888f
Draft

Remove green elephant markers from what-is-baml headings#4598
ATX24 wants to merge 1 commit into
canaryfrom
cursor/remove-green-elephant-markers-888f

Conversation

@ATX24

@ATX24 ATX24 commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Pull Request Template

Thanks for taking the time to fill out this pull request!

Issue Reference

Please link to any related issues

  • This PR fixes/closes #[issue number]

Changes

Please describe the changes proposed in this pull request

  • Removed the {elephant} prefix markers from the four "elephant in the room" section titles on app/what-is-baml/page.tsx.
  • Removed the now-unused placeholder art entries tied to those markers.
  • Updated nearby inline comments to reflect the new behavior.

Testing

Please describe how you tested these changes

  • Unit tests added/updated
  • Manual testing performed
  • Tested in local dev environment

Validation run:

  • pnpm exec biome check app/what-is-baml/page.tsx
  • pnpm typecheck ❌ (fails due to pre-existing unrelated workspace issues, e.g. missing generated pkg-proto modules and existing TenetsAccordion.tsx type errors)

Screenshots

If applicable, add screenshots to help explain your changes

  • N/A (content-only heading marker removal)

PR Checklist

Please ensure you've completed these items

  • I have read and followed the contributing guidelines
  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings

Additional Notes

Add any other context about the PR here

  • This is a minimal UI cleanup to remove the green placeholder markers shown before those headings in production.

Slack Thread

Open in Web Open in Cursor 

Co-authored-by: Dhilan Shah <ATX24@users.noreply.github.com>
@vercel

vercel Bot commented Aug 26, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
beps Ready Ready Preview Aug 26, 2026 6:11am
promptfiddle2 Ready Ready Preview Aug 26, 2026 6:11am

Request Review

@coderabbitai

coderabbitai Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

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

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown

⏭️ Performance benchmarks were skipped

Perf benchmarks (CodSpeed) are opt-in on pull requests — they no longer run on every push. They always run automatically after merge to canary/main.

To run them on this PR, do any of the following, then push a commit (or re-run CI):

  • Add RUN_CODSPEED=1 to the PR description, or
  • Include run-perf or /perf in the PR title or any commit message.

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