3 ms·
I’m glad this article mentions GitHub, who have had some of the best URL design I’ve ever seen, and have done since they first launched. I use that ALL the tim
by simonw 2y ago
I’m glad this article mentions GitHub, who have had some of the best URL design I’ve ever seen, and have done since they first launched.
I use that ALL the time. I can navigate straight to any issue by typing a URL. I can switch to the “actions” view for a repo by adding /actions. I can see the file I’m looking at in a branch by editing the URL and swapping “main” for the branch name.
All available via the UI as well, but I interact with GitHub so often that the tiny efficiency boost I get from navigating by URLs really starts to add up.
I also trust them not to break links, based on their track record. My notes and blog posts and even my source code are full of links to issues or code snippets on GitHub.
- c-hendricks 2y agodo these routes on github irk anyone else: /issues/ /issues/:id /pulls/ /pull/:id
- heinrich5991 2y agoEven worse: /issues/ /issues/:id /pulls/ /pulls/:author /pull/:id
- simonw 2y agoYes! I really wish they would at least set up /pulls/:id to redirect to /pull/:id
- berkes 2y agoI believe this is a (happy) legacy from Rails. In rails, if you don't spend effort to undo, you get URLs that match your database setup in a RESTful way. For me, that's far to tight coupling, and problematic in other ways. But the result is that without thinking about it, without a second of time spent on designing an URL structure, you get a very nice, consistent and clean one for free.