Programming

A few weeks ago, I threw down a CLI for getting web-links for a local repo, so you could e.g. run forge path docs/index.md and it would give you a permalink for your GitHub/Codeberg/etc. repo to that index.md file.
Now I've used it for a few weeks and I'm realizing all the dumb assumptions I've made about how Git repos work.

For example, there's also a subcommand forge issue 123, which gives you a link to issue #123, but of course, it's not necessarily true that you actually have your issues where your code lives. You might have a separate JIRA, or you might be working on a fork from which you'll post a PR later.

Now I'm trying to figure out how to make it work at the very least for my own use-cases, ideally without requiring configs for every repo.

But yeah, it's great fun. Some excellent puzzles and also very humbling, because I'm pretty much supposed to be an expert in Git and yet:

1. you suddenly see me googling shit like "git fetch vs. push url", and
2. I struggle just as much to formulate proper requirements as our customers at $DAYJOB.