home.social

#commithistory — Public Fediverse posts

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

fetched live
  1. @fedora Darned if I know. I know it predates Fedora, probably Red Hat Linux 5.2-ish? It would have had something to do with #MkLinux

    *Actual* Fedora contributions? Would have been indirectly via #Fuduntu, back around FC13-ish?

    In any case, a long time ago. And the memory isn't what it once was.

    #CommitHistory

  2. @fedora My first way of contributing to #Fedora happened over IRC. As I was trying to figure out how to do #Linux, I found others would ask the questions I asked before, so I could pass on what I just learned to them, and ended up sticking around more intentionally to help other users just as the community had helped me.

    #CommitHistory

  3. We're looking for Fedora contributors to share how they started collaborating in the project! Use to talk about what your first contribution was and what it was like. Some stories will be put together into a Fedora Magazine article to be featured ahead of Flock (June 14-16)!

    Learn more: fedoramagazine.org/commit-hist

  4. I hereby propose that the Conventional Commits standard is expanded by the commit type `tmp:`

    > This commit type is used for placeholder work that is intentionally messy, unsquashable, and unreviewable. This type of commit is only meant to exist as a transient solution in the codebase, and the reasons for its presence are not subject to questioning. It serves a functional but impermanent purpose.

    Characteristics:
    - Cannot be squashed in a clean-up process.
    - Often contains quick, messy, or experimental code.
    - Reserved for situations where there’s an unspoken reason for its existence, known only to the contributor.

    #Git #ConventionalCommits #CommitHistory #GitSquash