26
.gitignore Isn’t the Only Way To Ignore Files in Git (nelson.cloud)
submitted 4 months ago by to c/git@programming.dev
4 comments fedilink hide all child comments

all 4 comments

sorted by: hot top controversial new old
[–] 5 points 4 months ago (2 children)

I got a bunch of rules in the exclude file for my own personal trash files in the repo. I’m not a happy man unless I can do git commit -am freely.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 14 points 4 months ago (1 child)

    git commit -am is for weirdos.

    You should do a git add .. Then do a git status. Then do git reset because . meant that all the stuff you didn't want to commit also is now in the staging area, then do a manual git add <dst_path> for your paths. Then do a git add . by accident, and repeat.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
    • [–] 2 points 4 months ago

    Thanks! That'll be useful to keep my ad-hoc degug files out of the git status list

  • permalink
  • fedilink
  • source
    •
    1 comment in c/webdev@programming.dev view that post
    [–] 5 points 4 months ago

    WHEN there are multiple, contradictory, config-files,

    THEN every single 1 of those bastards ought be explicitly-identified, in the 1st-line-comment, in ALL of them, so that all configurators of any of them know there may be overrides.

    Externalize the damn memorization!

    There is plenty of research identifying that parallel-IFs, and equivalent parallel/contradictory config/logic structures, are BIG bug-sources.

    Ask any sysadmin who has fought config in Linux distros, due to this antipattern.

    Make all the locations be named, in every such config, every fscking time!

    "Spanish Inquisition" surprises can go eat rocks.

    🙏

  • permalink
  • fedilink
  • source
    •