Show newer

subtoot, caps 

some post:

---
PLEASE REBLOG THIS WARNING

<important warning about epilepsy>
---

Why didn't you use a CW? why are you shouting?

Why didn't you do this:

---
Important warning about the new Venom movie for people with epilepsy [show more]

<important warning>

(please boost!)"
---

instead of freaking people about by yelling, you're letting them choose to engage. Additionally, you're putting more information in the cw, so people see what you're talking about immediately.

Classic Doctor Who :: [ Season 6 ] 

Interesting tidbit I just read about The Invasion (which I've nearly finished watching now) – this was the last story to feature the cybermen until 1975 (7 years later)

Show thread

git question, addressing everyone's responses 

Unfortunately it's part of a build system, so I can't rename it - it has to be stack.yaml

I can't set it to work on both because I need these lines on my system:

nix:
enable: true

and those lines don't work without nixos.

I can't use the global gitignore because I have stack.yaml in other repositories that use stack, and I have to commit the file in those.

and the .git/info/exclude file doesn't seem to work

Show thread

git question 

@loki @catoutofbed@octodon.social I can't do that, because other projects NEED me to track the stack.yaml file

git question 

@loki @catoutofbed@octodon.social this does not appear to work:

re: git question 

@rachel yeah, I find git gets in the way a lot more than it should

git question 

@CobaltVelvet@octodon.social I know, but I'm used to typing "git commit -a".

I can change my behaviour, but I'd like to have the computer prevent me from making the mistake in the first place, if possible

git question 

@loki @catoutofbed@octodon.social there's already a gitignore file, so if I modified it I'd now have to make sure not to send the change to the gitignore file upstream

re: git question 

@rachel the problem is I keep having to revert my branches because I accidentally type "git commit -a"

(because I'm used to a mercurial workflow)

git question 

I'm working in a repository made by someone else, and it includes a build file.

This build file should NOT change upstream, however in order for it to build on my system I needed to make some OS-specific changes to the file.

Is there a way to tell git "hey, don't commit this file, and just leave it the way it is" without either removing my modifications to the file or sending my modifications upstream?

Show older
Computer Fairies

Computer Fairies is a Mastodon instance that aims to be as queer, friendly and furry as possible. We welcome all kinds of computer fairies!