• SuperFola@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    “fix ci” “Again” “Maybe?”

    Every time I work on CIs I just lose it after 1 or 2 commits and squash merge later on. Also when integrating projects together (eg I’m working on a language and made a POC for a new parser in a separate project) I’m just like “hajzjgkzlabai yes”

  • kabat@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    I use a single dot when committing to a feature branch. I will either rebase or merge --squash anyway, so what’s the point really.

    e: in my private projects that is, I use a jira ticket number at work, because I have to.

  • blurr11@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    For personal stuff especially when I use git just to sync between laptop and computer most of my commits are the things that don’t work and I use for new stuff ~for changes and X for broken stuff.

    So a commit can be " + new feature ~logging to accommodate new feature X Edge case crashes the new feature."

  • Mert Şişmanoğlu@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Worst commit that i pushed receantly was git commit -m "._." for my personal js practice repo. I needed it because all of the content is “CRLF” but I’m using “LF” on my machine.