home.social

#saplingscm — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #saplingscm, aggregated by home.social.

fetched live
  1. Caoilte O'Connor @[email protected] ·

    My favourite new word at work is #prefactor as in, "Hey #claude Please prefactor the ugly code in this business logic feature change PR so that it is easier to read?"

    The refactoring lands in a preparatory PR and everyone gets to review a much easier to understand business logic change follow-up PR.

    I suspect the flow would get even nicer if I could find time to skill-up with claude on #jj (or possibly even better #SaplingSCM - since reviews are still the biggest bottleneck)

    #prefactor #claude #jj #saplingscm
  2. Diego Elio Pettenò @[email protected] ·

    So it s weekend, and I'm now playing around with using #SaplingSCM with @zephyr (at least locally, I _might_ try this for draft pull requests, but I doubt I can get people behind Review Board.)

    Should I write a blog about this? Let me know by donating to #Diabetes UK!

    tiltify.com/@flameeyes/gone-wi

    #saplingscm #diabetes
  3. François 🇨🇦 @[email protected] ·

    I did some more tests today with #saplingscm. I made two commits, and 2 PRs using `sl pr`. This pushed and created 2 PRs on GitHub. When I rebased & merged the 1sr PR, `sl pull` said “one commit landed” meaning it noticed that the 1st PR had been added to master.

    After that, I `sl restack -d master` (an equivalent to `git rebase master`) and ran `sl pr`. This pushed an updated commit to GitHub. I then squash merged PR2 on GitHub, and the next `sl pull` told me that it saw the landed commit.

    #saplingscm