Skip to content

feat(github): add 16 PR celebration message templates#1088

Merged
muddlebee merged 2 commits intoTracer-Cloud:mainfrom
muddlebee:cursor/more-meme-pr-celebration-messages
Apr 29, 2026
Merged

feat(github): add 16 PR celebration message templates#1088
muddlebee merged 2 commits intoTracer-Cloud:mainfrom
muddlebee:cursor/more-meme-pr-celebration-messages

Conversation

@muddlebee
Copy link
Copy Markdown
Collaborator

Fixes #

Describe the changes you have made in this PR -

Adds 16 new unhinged/meme-tier message templates to .github/scripts/merged_pr_celebration_message.py, the script that posts a celebration comment whenever a PR is merged.

The original 8 templates already in main are untouched. The new ones are appended after a # new additions comment.

New templates cover:

  • "I said I'd fix it and fixed it" — hall of fame behavior
  • Pizza theory (crispy edges, no unnecessary toppings)
  • Git history permanence ("no take-backs, no refunds, we love you")
  • CI/linter standing ovation
  • Maintainers feared them, linters respected them, CI genuflected
  • "Stop making the rest of us look bad, we're begging"
  • Rebase handled, conflicts squashed, CI fully vibing
  • Retire the jersey
  • Researchers baffled — broken the known laws of open source
  • Perfect taco energy
  • Ascending to final form (dragon lore)
  • Alien threat assessment upgrade
  • Poet arc ("it was always about this PR")
  • Tea-speed merge ("elite performance, no notes")
  • Skipped review purgatory, merged like it owned the place
  • Interview skit with line-break dialogue

Also fixes a broken f-string in the scientists/baffled template where @{contributor} was in a plain string instead of an f-string.


Code Understanding and AI Usage

Did you use AI assistance (ChatGPT, Claude, Copilot, etc.) to write any part of this code?

  • No, I wrote all the code myself
  • Yes, I used AI assistance (continue below)

If you used AI assistance:

  • I have reviewed every single line of the AI-generated code
  • I can explain the purpose and logic of each function/component I added
  • I have tested edge cases and understand how the code handles them
  • I have modified the AI output to follow this project's coding standards and conventions

Explain your implementation approach:

The script picks a random template and a random GIF from their respective lists. Adding more templates reduces repeat frequency — pool grows from 8 to 24. All new entries follow the same f-string pattern as the originals. Script was smoke-tested locally with DISCORD_INVITE_URL and CONTRIBUTOR_LOGIN env vars to verify all interpolations render correctly.


Checklist before requesting a review

  • I have added proper PR title and linked to the issue
  • I have performed a self-review of my code
  • I can explain the purpose of every function, class, and logic block I added
  • I understand why my changes work and have tested them thoroughly
  • I have considered potential edge cases and how my code handles them
  • If it is a core feature, I have added thorough tests
  • My code follows the project's style guidelines and conventions

Note: Please check Allow edits from maintainers if you would like us to assist in the PR.

- add 16 new unhinged/humorous message templates to the post-merge comment script
- cover themes: rubber duck debugging, pizza theory, git history permanence,
  alien threat assessment, tea-speed merges, interview skit, poet arc, and more
- fix broken f-string interpolation in scientists/baffled template
- original 8 templates in main left untouched
@muddlebee muddlebee marked this pull request as ready for review April 29, 2026 19:38
@muddlebee muddlebee merged commit a952ed3 into Tracer-Cloud:main Apr 29, 2026
1 check passed
@muddlebee muddlebee changed the title feat(github): add 16 meme-tier PR celebration message templates feat(github): add 16 PR celebration message templates Apr 29, 2026
@github-actions
Copy link
Copy Markdown
Contributor

🏆 @muddlebee did not come to play. PR opened. Review survived. Merged clean. Retire the jersey. 🎽


👋 Join us on Discord - OpenSRE : hang out, contribute, or hunt for features and issues. Everyone's welcome.

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Apr 29, 2026

Greptile Summary

This PR adds 16 new meme-tier celebration message templates to the merged-PR comment script, expanding the random-pick pool from 8 to 24. All new entries are purely additive, follow the existing f-string pattern, and correctly interpolate {contributor} in f-strings.

Confidence Score: 5/5

Safe to merge — all 16 templates are syntactically correct and the only findings are minor style inconsistencies.

All P0/P1 criteria are clear: every {contributor} placeholder lives inside an f-string, Python string concatenation is valid throughout, and the script logic is unchanged. The two P2 findings (unnecessary f prefixes and missing trailing comma) are cosmetic and do not affect runtime behaviour.

No files require special attention.

Important Files Changed

Filename Overview
.github/scripts/merged_pr_celebration_message.py Appends 16 new meme-tier celebration templates; all {contributor} interpolations are in valid f-strings; minor: 5 strings carry an unnecessary f prefix and the last entry lacks a trailing comma.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[GitHub Actions: PR Merged] --> B[merged_pr_celebration_message.py]
    B --> C{Read env vars}
    C --> D[CONTRIBUTOR_LOGIN → contributor]
    C --> E[DISCORD_INVITE_URL → discord]
    D & E --> F[random.choice from templates\n8 original + 16 new = 24 total]
    F --> G[random.choice from gif_blocks\n10 GIFs]
    G --> H[Assemble: template + gif + footer]
    H --> I[Write to comment.md]
    I --> J[Action posts comment.md\non merged PR]
Loading

Reviews (1): Last reviewed commit: "refactor(github): trim celebration templ..." | Re-trigger Greptile

Comment on lines +58 to +59
f"🤖 **CI passed. Linter didn't scream. Reviewer typed LGTM.** "
f"@{contributor}, every machine in this pipeline just slow-clapped. 🖥️✨"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

P2 Unnecessary f prefix on interpolation-free strings

Several first segments in the new multi-line string pairs carry an f prefix even though they contain no {...} placeholders — the rest of the file consistently omits f on those parts. Five occurrences in the new additions: lines 58, 66, 86, 94, and 102.

Suggested change
f"🤖 **CI passed. Linter didn't scream. Reviewer typed LGTM.** "
f"@{contributor}, every machine in this pipeline just slow-clapped. 🖥️✨"
"🤖 **CI passed. Linter didn't scream. Reviewer typed LGTM.** "
f"@{contributor}, every machine in this pipeline just slow-clapped. 🖥️✨"

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

f"💼 **Interviewer:** describe a time you shipped something impactful.\n\n"
f"**@{contributor}:** *points at this PR*\n\n"
"**Interviewer:** you're hired. 🤝"
)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

P2 Missing trailing comma on last list element

All other entries in templates end with ,. The final new entry drops it, diverging from the consistent style of the list and making future append diffs noisier.

Suggested change
)
),
]

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

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