[WIP] Add LinkedIn post template for Formbricks contributions

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original prompt

Draft a short LinkedIn post template in the repository (e.g., docs or a markdown file) that highlights recent Formbricks open-source contributions and explains why they are noteworthy. Include a concise summary and suggested hashtags.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: Tell me the initial changes , from those the maintainer "charlesBochet" did some changes with the commits , tell me this pr got merged are my changes left or is this pr good to showcase on my resume ?

Assistant: Short answer: Your original change (disabling auto‑dismiss for error snackbars) was reverted by the maintainer, and the final merged PR reflects their revised behavior, not your initial logic. You can still showcase this PR on your resume, but be clear that you authored the initial proposal and the final implementation was adjusted by the maintainer.

Initial changes you made (your first commit):

• Disabled the default 6s auto‑dismiss for error snackbars unless an explicit duration was provided.
• Kept non‑error snackbars auto‑dismissed by default.
• Tied progress bar visibility/animation to auto‑dismiss.

Maintainer (charlesBochet) changes after your commit:

• Reverted the error‑specific duration logic (restored default 6s auto‑dismiss for all variants).
• Added a bottom button action UI (renamed props from action* → button*).
• Updated progress bar styling (full height), padding, and Storybook stories.
• Added button navigation (buttonTo) and spacing tweaks.

Are your changes still in the final merged PR?

• The core behavior change you introduced (no auto‑dismiss for errors) was not kept.
• Your PR still matters as the starting point, but the final merged behavior is the maintainer’s revised approach.

Resume guidance:

• ✅ You can showcase it as a merged OSS contribution.
• ✅ Emphasize collaboration and that the PR was merged after maintainer refinements.
• ✅ Phrase it like: “Proposed UX changes for SnackBar behavior; collaborated with maintainer on final implementation and UI improvements.”

If you want, I can craft a resume bullet tailored to this PR or pull the exact final diff for a precise summary.

User: @kysely-org/kysely/pull/1720
@twentyhq/twenty/pull/19712
@formbricks/formbricks/pull/7735
@formbricks/formbricks/pull/7497

These are my 4 best prs from which one is open and 3 are merged , tell me 2 resume worthy prs from these and why , i am targeting sde roles(full stack , frontend , backend) in remote startups like in usa , eu etc and even mncs

Assistant: Pick these two for your resume:

1. fix: prevent bypass of single-use survey restriction via v1 API formbricks/formbricks#7735 — “prevent bypass of single-use survey restriction via v1 API” (merged)
   Why: It’s a security + backend correctness fix with clear business impact (prevents abuse of single‑use links). You added validation, URL parsing, optional decryption, and error handling. This signals strong backend and API design skills that startups/MNCs value.

2. feat: enhance welcome card to support video uploads and display #7491 formbricks/formbricks#7497 — “enhance welcome card to support video uploads” (merged)
   Why: It’s a full‑stack product feature touching UI and survey rendering, adding video media support and improving data handling. This shows frontend + product UX impact, which is great for full‑stack and frontend roles.

Why not the other two (for top 2):

• feat: add IF EXISTS support for alter table kysely-org/kysely#1720 (open): Good backend library feature, but still unmerged. You can keep it as a “submitted PR” mention, but merged work usually ranks higher on a resume.
• Refactor SnackBar duration handling and progress bar visibility logic twentyhq/twenty#19712 (merged): The final merged behavior was substantially modified by the maintainer (your core behavior change was reverted), so it’s less clean to present as your impact.

If you want, I can craft resume bullet points for the two picks tailored to SDE/full‑stack roles.

User: But the prs you are giving are from same saas only

Assistant: Got it — if you want two resume‑worthy PRs from different products, I’d pick:

1. fix: prevent bypass of single-use survey restriction via v1 API formbricks/formbricks#7735 (merged) — security + backend correctness
2. feat: add IF EXISTS support for alter table kysely-org/kysely#1720 (open) — database library feature (ALTER TABLE IF EXISTS)

Why this mix: it shows backend security/API work in a SaaS and core library/SQL feature work in an open‑source DB toolkit — different domains, stronger breadth.

If you prefer merged-only, the cross‑product pick would be:

• fix: prevent bypass of single-use survey restriction via v1 API formbricks/formbricks#7735 (merged)
• Refactor SnackBar duration handling and progress bar visibility logic twentyhq/twenty#19712 (merged, but note the final behavior was revised by the maintainer)

Tell me which constraint you want (merged‑only vs cross‑product), and I’ll finalize the two and draft resume bullets.

User: there is no constraint

Assistant: Great—no constraints. My top two resume‑worthy PRs (overall strongest impact + signal) are:

1. fix: prevent bypass of single-use survey restriction via v1 API formbricks/formbricks#7735 — “prevent bypass of single‑use survey restriction via v1 API” (merged)
   Why: Security + backend correctness...

This pull request was created from Copilot chat.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
resume-forge-ai	Ready	Preview, Comment	May 1, 2026 9:32am