cloudyluna

{
  "nodes": {
    "flake-utils": {
      "inputs": {
        "systems": "systems"
      },
      "locked": {
        "lastModified": 1731533236,
        "narHash": "sha256-l0KFg5HjrsfsO/JpG+r7fRrqm12kzFHyUHqHCVpMMbI=",
        "owner": "numtide",

cloudyluna

First, we meow.
Second, we eep.
Third, we meow.
And finally, we eep.

cloudyluna

{- cabal:
  build-depends: base
  default-language: GHC2021
-}
import Control.Arrow (Arrow, first, second, arr, (>>>))
import Control.Category (Category)
import qualified Control.Category
import Control.Monad

newtype SF i o = SF { runSF :: (i -> o) }

cloudyluna

Git Commit Best Practices

Basic Rules

Commit Related Changes

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.

Commit Often

Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.