I recommend checking out the Forgejo repo itself and potentially report your issues there, in case they aren't documented
Ok, nvm. I think the best path forward is, as you mentioned, to just state the single Forgejo version, that the current version of the crate supports. We should make it clear, that essentially...
Can you describe the concrete issues you encountered? Just so I have a clearer idea what is going on
The response bodies and headers are identical
Just to be sure, I'm assuming you are talking about line 874. I don't quite get what you mean. If the user queries whether they starred a given repo and they didn't, it doesn't imply that they...
I'll get to that later. This is also something to be fixed in the watch-status command.
Definitely more terse, although I'm not too much of a fan of using anything else than a string literal as the argument for the ftl_ macros. This wouldn't really make the code simpler in my opinion.
In this case we need to make a second API call to determine whether the repo exists. Unfortunately, Codeberg uses a 404 to signal the status as unstarred/unwatched, so we can not distinguish that...
I second this. Can it be used by AI: yes. But so can pretty much everything automated. Apart from allowing currently not covered endpoints it may also allow users to target endpoints, we already...
Rebased onto current main and I took the opportunity to also add help text for the --list flag
Applied the same changes for printing all starred repos as in #560