home.social

#vcs — Public Fediverse posts

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

fetched live
  1. Lobsters @[email protected] ·

    Comments in the code vs PR description lobste.rs/s/2dsufc #practices #vcs
    devblogs.microsoft.com/oldnewt

    #practices #vcs
  2. Lobsters @[email protected] ·

    Comments in the code vs PR description lobste.rs/s/2dsufc #practices #vcs
    devblogs.microsoft.com/oldnewt

    #practices #vcs
  3. Lobsters [Unofficial] @[email protected] ·

    Comments in the code vs PR description

    fed.brid.gy/r/https://devblogs

    #practices #vcs
  4. Lobsters @[email protected] ·

    GitHub Stacks in Jujutsu by @alannorbauer lobste.rs/s/keiw21 #vcs
    alan.norbauer.com/articles/git

    #vcs
  5. Lobsters @[email protected] ·

    GitHub Stacks in Jujutsu by @alannorbauer lobste.rs/s/keiw21 #vcs
    alan.norbauer.com/articles/git

    #vcs
  6. Lobsters [Unofficial] @[email protected] ·

    GitHub Stacks in Jujutsu

    fed.brid.gy/r/https://alan.nor

    #vcs
  7. Lobsters @[email protected] ·

    Who Should Pay For Source Code Availability? via @hugoarnal lobste.rs/s/rsztog #vcs #zig
    kristoff.it/blog/source-code-a

    #vcs #zig
  8. Lobsters @[email protected] ·

    Who Should Pay For Source Code Availability? via @hugoarnal lobste.rs/s/rsztog #vcs #zig
    kristoff.it/blog/source-code-a

    #vcs #zig
  9. Lobsters [Unofficial] @[email protected] ·

    Who Should Pay For Source Code Availability?

    fed.brid.gy/r/https://kristoff

    #vcs #zig
  10. Brian Davis @[email protected] ·

    I just spent a couple days working on an old project that still has the code in mercurial and damn it. Now I'm sad all over again that git won that popularity contest.

    #vcs #git #mercurial

    #vcs #git #mercurial
  11. Brian Davis @[email protected] ·

    I just spent a couple days working on an old project that still has the code in mercurial and damn it. Now I'm sad all over again that git won that popularity contest.

    #vcs #git #mercurial

    #vcs #git #mercurial
  12. Lobsters @[email protected] ·

    Radicle 1.10.0 – Sunflower via @robinheghan lobste.rs/s/ahuerd #vcs
    radicle.dev/2026/08/05/radicle

    #vcs
  13. Lobsters @[email protected] ·

    Radicle 1.10.0 – Sunflower via @robinheghan lobste.rs/s/ahuerd #vcs
    radicle.dev/2026/08/05/radicle

    #vcs
  14. Lobsters @[email protected] ·

    jujutsu 0.44.0 lobste.rs/s/xx83dr #release #vcs
    github.com/jj-vcs/jj/releases/

    #release #vcs
  15. Lobsters @[email protected] ·

    jujutsu 0.44.0 lobste.rs/s/xx83dr #release #vcs
    github.com/jj-vcs/jj/releases/

    #release #vcs
  16. Lobsters [Unofficial] @[email protected] ·

    jujutsu 0.44.0

    fed.brid.gy/r/https://github.c

    #release #vcs
  17. Jeff Forcier @[email protected] ·

    #jujutsu #vcs still lots of fun to use (I've since updated my default tmux session config to stop popping out #git related panes like lazygit) but also still getting my head around best practices and ergonomics.

    E.g., `jj bookmark advance` clearly prefers that your head/@ be a "real commit"; if you're sitting on an empty commit after a `jj new` or `jj commit` or etc, you have to remember to say `jj bookmark advance --to @-` which is easy to forget.

    Conversely, jj's behavior of "@ contains your working copy as-is, there's no index/staging" means you're incentivized /not/ to be sitting on "real work" lest you accidentally perform the equivalent of `git commit --amend` every time you edit a file. (This bites me a lot! Especially for files that another tool is auto-updating like uv.lock, Pulumi.$env.yml etc.)

    #jujutsu #vcs #git
  18. Jeff Forcier @[email protected] ·

    #jujutsu #vcs still lots of fun to use (I've since updated my default tmux session config to stop popping out #git related panes like lazygit) but also still getting my head around best practices and ergonomics.

    E.g., `jj bookmark advance` clearly prefers that your head/@ be a "real commit"; if you're sitting on an empty commit after a `jj new` or `jj commit` or etc, you have to remember to say `jj bookmark advance --to @-` which is easy to forget.

    Conversely, jj's behavior of "@ contains your working copy as-is, there's no index/staging" means you're incentivized /not/ to be sitting on "real work" lest you accidentally perform the equivalent of `git commit --amend` every time you edit a file. (This bites me a lot! Especially for files that another tool is auto-updating like uv.lock, Pulumi.$env.yml etc.)

    #jujutsu #vcs #git
  19. Lobsters @[email protected] ·

    wiff via @jparise lobste.rs/s/tc82u0 #practices #vcs
    wezfurlong.org/wiff/

    #practices #vcs
  20. Lobsters @[email protected] ·

    wiff via @jparise lobste.rs/s/tc82u0 #practices #vcs
    wezfurlong.org/wiff/

    #practices #vcs
  21. Lobsters [Unofficial] @[email protected] ·

    wiff

    fed.brid.gy/r/https://wezfurlo

    #practices #vcs #vibecoding
  22. dorotaC @dcz ·

    So... How do I start a SHA-256 repository?
    Can I convert an existing one?

    Is there an easy alias for git init?

    #git #versioncontrol #vcs #programming
  23. dorotaC @[email protected] ·

    So... How do I start a SHA-256 #git repository?
    Can I convert an existing one?

    Is there an easy alias for git init?

    #versioncontrol #vcs #programming

    #git #versioncontrol #vcs #programming
  24. Lobsters @[email protected] ·

    Accepting a messy git history lobste.rs/s/aj7msu #practices #vcs
    beza1e1.tuxen.de/git_two_users

    #practices #vcs
  25. Lobsters @[email protected] ·

    Accepting a messy git history lobste.rs/s/aj7msu #practices #vcs
    beza1e1.tuxen.de/git_two_users

    #practices #vcs
  26. Lobsters [Unofficial] @[email protected] ·

    Accepting a messy git history

    fed.brid.gy/r/https://beza1e1.

    #practices #vcs
  27. Lobsters @[email protected] ·

    Stacked pull requests are now in public preview - GitHub Changelog lobste.rs/s/pzl6f0 #vcs
    github.blog/changelog/2026-07-

    #vcs
  28. Lobsters @[email protected] ·

    Stacked pull requests are now in public preview - GitHub Changelog lobste.rs/s/pzl6f0 #vcs
    github.blog/changelog/2026-07-

    #vcs
  29. Lobsters @[email protected] ·

    Manganin: tools matter lobste.rs/s/c9xa6h #vcs #zig
    blog.manganin.dev/blog/tools-m

    #vcs #zig
  30. Lobsters @[email protected] ·

    Manganin: tools matter lobste.rs/s/c9xa6h #vcs #zig
    blog.manganin.dev/blog/tools-m

    #vcs #zig
  31. Lobsters [Unofficial] @[email protected] ·

    Manganin: tools matter

    fed.brid.gy/r/https://blog.man

    #vcs #zig
  32. Lobsters @[email protected] ·

    Make Reviews Possible Again With This One Simple Trick lobste.rs/s/2shapa #programming #vcs #vibecoding
    silky.github.io/posts/reviews-

    #programming #vcs #vibecoding
  33. Lobsters @[email protected] ·

    Make Reviews Possible Again With This One Simple Trick lobste.rs/s/2shapa #programming #vcs #vibecoding
    silky.github.io/posts/reviews-

    #programming #vcs #vibecoding
  34. Lobsters @[email protected] ·

    What does GitHub’s security team even do? lobste.rs/s/jnhyrh #security #vcs
    orchidfiles.com/github-securit

    #security #vcs
  35. Lobsters @[email protected] ·

    What does GitHub’s security team even do? lobste.rs/s/jnhyrh #security #vcs
    orchidfiles.com/github-securit

    #security #vcs
  36. Lobsters [Unofficial] @[email protected] ·

    Make Reviews Possible Again With This One Simple Trick

    fed.brid.gy/r/https://silky.gi

    #vcs #programming #vibecoding
  37. Lobsters [Unofficial] @[email protected] ·

    What does GitHub’s security team even do?

    fed.brid.gy/r/https://orchidfi

    #security #vcs
  38. Lobsters @[email protected] ·

    git rebase -i is not that scary via @hugoarnal lobste.rs/s/uawqly #vcs
    cachebag.sh/journal/interactiv

    #vcs
  39. Lobsters @[email protected] ·

    git rebase -i is not that scary via @hugoarnal lobste.rs/s/uawqly #vcs
    cachebag.sh/journal/interactiv

    #vcs
  40. Lobsters [Unofficial] @[email protected] ·

    git rebase -i is not that scary

    fed.brid.gy/r/https://cachebag

    #vcs
  41. Some Bits: Nelson's Linkblog @[email protected] ·

    Evan's Jujutsu tutorial: New tutorial from an engineer with particular expertise
    evmar.github.io/jjtut/
    #versioncontrol #programming #jujutsu #git #vcs #jj #+

    #versioncontrol #programming #jujutsu #git #vcs #jj
  42. Lobsters @[email protected] ·

    Web-based Jujutsu revset explorer & debugger lobste.rs/s/xroult #vcs
    juju.bi/tools/revset

    #vcs
  43. Lobsters @[email protected] ·

    Web-based Jujutsu revset explorer & debugger lobste.rs/s/xroult #vcs
    juju.bi/tools/revset

    #vcs
  44. Lobsters @[email protected] ·

    git --end-of-options via @robalex lobste.rs/s/cxz7vd #vcs
    nesbitt.io/2026/07/21/end-of-o

    #vcs
  45. Lobsters @[email protected] ·

    git --end-of-options via @robalex lobste.rs/s/cxz7vd #vcs
    nesbitt.io/2026/07/21/end-of-o

    #vcs
  46. Lobsters @[email protected] ·

    GitHub suddenly rejected my SSH key (the fix was a .pub file?!) lobste.rs/s/twqtlo #devops #vcs
    thorsell.io/2026/07/21/github-

    #devops #vcs
  47. Lobsters [Unofficial] @[email protected] ·

    GitHub suddenly rejected my SSH key (the fix was a .pub file?!)

    fed.brid.gy/r/https://thorsell

    #devops #vcs