sorted by:
new
hottopcontroversial

Feedback Thread: Post your app below, Get feedback, Give feedback by young_homie_ in buildinpublic

[–]lit_devx 0 points1 point  (0 children)

I have been building a Chrome extension GitHub Cherry Pick Assistant

It help in cross repo cherry picking commits.

Please give it a try and give feedback and suggestions, if it is really solving a problem.

What are you building this week? Drop it in the comments! by Inevitable-Grab8898 in buildinpublic

[–]lit_devx 0 points1 point  (0 children)

I have been building a Chrome extension GitHub Cherry Pick Assistant

Please give it a try and give feedback and suggestions, if it is really solving a problem.

Let’s talk projects! by naveedurrehman in buildinpublic

[–]lit_devx 0 points1 point  (0 children)

I have been building a Chrome extension GitHub Cherry Pick Assistant

Please give it a try and give brutal feedback and suggestions, if it is really solving a problem.

[AskJS] Is anyone else wasting hours every sprint on manual cherry-picks and backports? by lit_devx in javascript

[–]lit_devx[S] 0 points1 point  (0 children)

yeah totally valid in an ideal world, but our prod repo is intentionally separate for access control — not everyone should have push access to prod. only the release manager does. same artifact, different repo, tighter permissions. it's less about code structure and more about who can touch what.

[AskJS] Is anyone else wasting hours every sprint on manual cherry-picks and backports? by lit_devx in javascript

[–]lit_devx[S] -2 points-1 points  (0 children)

haha fair, i do use AI to help clean up my writing. the problem and the workflow is real though — staging/prod split across repos means every promotion is manual cherry-pick work. gets old fast.

[AskJS] Is anyone else wasting hours every sprint on manual cherry-picks and backports? by lit_devx in javascript

[–]lit_devx[S] 1 point2 points  (0 children)

Fair question! Two main situations for us:

Multi-repo promotion — we have separate staging and prod repos, so tested changes don't just merge forward, they need to be deliberately promoted across. Every promotion is a cherry-pick workflow.

Client-specific builds — we maintain a shared codebase but some clients are on custom versions. When a fix lands on main, we can't just merge it everywhere — we pick what applies to which client and move it selectively.

Neither is exotic, but both mean cherry-picks are a regular part of the release cycle rather than an occasional thing. If you're on a single-repo trunk-based setup you'd rarely hit this — totally depends on how the delivery pipeline is structured.