Pretty URLs #15
reinhard
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, the JSON endpoint is something like
https://api.reuse.software/api/project?url=https://git.fsfe.org/reuse/website, and the badgehttp://api.reuse.software/badge?url=https%3A%2F%2Fgit.fsfe.org%2Freuse%2Fwebsite(URL encoded, but even decoded it wouldn't be pretty).It would be nice to have prettier URLs, although I guess that this will be a bit hard since we allow all kinds of source forges, for instance also
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/where the structure does not follow the commonhost.com/user/reposcheme.Would
https://api.reuse.software/status/https/git.fsfe.org/reuse/websitebe better?Depending on how we decide on #3, we could even shorten this to
https://api.reuse.software/status/git.fsfe.org/reuse/website.The entry points could be:
https://api.reuse.software/registerfor project registrationhttps://api.reuse.software/confirm/...?signature=...for project registration confirmationhttps://api.reuse.software/info/...for the nice human readable info page (#14)https://api.reuse.software/status/...for the JSON status informationhttps://api.reuse.software/badge/...for the badgeIs this closer to what you'd envision?
Yes to all, and
https://api.reuse.software/status/git.fsfe.org/reuse/websitewould be perfectly fine!This seems reasonable to me, with the following remark:
The reason I included the entire URL as a query string is because I figured that that would support basically anything, so long as you can
git cloneit. By changing to the above format, there might be some edge cases that may no longer be supported. For 99% of projects, however, it will probably work.