I think I got the idea. So essentially a new copy of the file is created and stored only if there is a change, else it just refer to the older SHA. Am I right? Now I understand why LFS was needed for binaries, else it createds a lot of storage problems, but not the huge monorepos.

I’m not a developer, but a design person who covers much more including architecture. But in my org I happen to teach developers how to use Git. Strange, I know. But that is the case. It gave me a good opportunity to learn Git in depth.

I went through your blogs and patch stack workflow. I have to say that I have not been happy with the branching workflow and I always felt that is not the best (I agree to the point about “unjust popularity”). The patch stack workflow makes more sense to me. Unfortunately we won’t be able to adopt, since getting everyone to Git itself was a huge effort. Also developers are not that keen into creating good code, but just working working code. I’m extremely frustrated with that.

Also your blog design is really good. I love it. I always wanted to create something like that. But never managed to sit down and do it. Can you give me a brief about the tech stack used for the blog?

Do you use RNote for diagrams? The style looks familiar. Or is it something else?

Aah. I assumed linting was part of the build also. My bad. I did understand the idea you were mentioning. Just that assumptions kind of threw me off.

I wanted to ask something related to that. As you mentioned, git takes a snapshot of the repo on every commit. So splitting up the bug fix and other activities means you have 3 or 4 commits instead of one. Let us say we are dealing with a very large repo. This does not look ideal in that context right? So do you think the way you proposed is only suitable for smaller repos?

Oh, never heard of amnezia. Never needed actually. But it looks like a good improvement on Wireguard. I will need a separate setup to test it out and currently I’m away from home with no clue when I will return. If I happen to find anything, I will definitely ping you.

In the HN page you linked many people mentioned v2ray. Have you tried that? How good is it?

Have you considered having Headscale on a cheap VPS? We are actually doing that and it is pretty capable. IIRC, you can configure not to use the tailscale servers at all, and use your own public VPS for coordination. Bonus point, tailscale hired the Headscale developer and maintainer, and they are allowed to work on Headscale while on their payroll. The team looks very much into FOSS.

So this bit confuses me. The article says in the intent and scope section that the entire process of bug fixing, in the included example, is literal bug fixing, clean up toggle, correct lints, correct duplication. That point to linting issues.

The earlier section says that a commit should be ‘buildable’ and ‘testable’. So if there are linting issues, the commit won’t satisfy this criteria right?

What am I missing here?

I found this in their GitHub repo.

Just out of curiosity, and I don’t know anything about testing.

Is uuv is equivalent to Playwright + Cucumber?

Tried neovim a couple of times. Stopped after 10 or 15 mins. Anyone has useful tips to get used to vim/neovim?

Giving you the benefit of doubt here.

“/s” technically means “this comment is sarcastic in nature”. But also commonly used with bad jokes and puns as well, indicating that this is indeed nonsense, and I’m aware of it, but I decided to say it anyway.

The previous comment was just a bad and cliche joke that is common in internet forums, referencing the “Skynet” from the “Terminator” movie series.

Your tricks won’t work, skynet! 😜 /s

“I hope this message finds you well”, is a marker I have been using to detect GPT replies. Looks like this is from ChatGPT.

Also it says “BLOB feature” and “BLOB functionality”. What in the coconut does that mean? “BLOB feature is an important aspect for our app.” Come on…

It’s really pathetic that they didn’t even try to read it at least once.

I have a different experience. There was one thread which linked to a github issue. The issue said some blobs don’t have source code. Ironically when I went on to check, the blobs mentioned in the issue had source code, but there were other blobs which seemed to miss the source or build instructions.

I would love to have an independent audit to put this issue at rest. All that happens is more and more noise and no resolution. I am not a programmer so can’t really help here.

Why? Can you elaborate?

Edit: oh, I automatically read it as J. Herkenhoff, and started to wonder what is the problem with the name.

The project already started to diverge. If you have an older version don’t update until you migrate.

This is a bit absurd. I really don’t think this is as serious as some comments say. Also there is a comment from AUR package manager which explains more details. . And even the blobs in the first post there are source and build instructions in their respective folder.

It works but I don’t think Forgejo plans to support it in the future. Gitea and Forgejo started to diverge and the documentation regarding docker is somewhat in a deprecated state.

Edit: I also think the OP’s question is different from this. So this might not be a solution.

Aah… I completely forgot about that. Will try next time. Also yesterday I saw Shift + F10 will show the context menu. Yet to test it on this site.

Yeah that’s true. The UI does not accurately represent the validation conditions.

Their desktop site is even more shitty. It won’t allow right click or paste actions. There goes compatibility with password managers.

Holy shit!! You did it. I would never expect a banking password to max special characters. I have been scratching my head with Bitwarden and this shitty app for an hour.