The latter is consistent with the GitHub status plugin.
With the current code, the working syntax for the token is:
```
token ${(import /etc/nixos/secret/gitea_tokens.nix).artiq-zynq}
```
and not
```
authorization = token ${(import /etc/nixos/secret/gitea_tokens.nix).artiq-zynq}
```
The latter is consistent with the GitHub status plugin.
Keeping it authorization was my oversight in #13. I am sorry for delivering broken code.
In the GithubStatus plugin the authorization key's value is copied as-is into the HTTP header Authorization. The token prefix will not be split away.
For the new GiteaStatus plugin the value is appended to the URI in the query parameter ?token=. Therefore I argue that token doesn't change terminology in the context of Gitea. Of course the final decision is up to you.
Keeping it `authorization` was my oversight in #13. I am sorry for delivering broken code.
In the **GithubStatus** plugin the `authorization` key's value is copied as-is into the HTTP header `Authorization`. The `token ` prefix will not be split away.
For the new **GiteaStatus** plugin the value is appended to the URI in the query parameter `?token=`. Therefore I argue that `token` doesn't change terminology in the context of Gitea. Of course the final decision is up to you.
With the current code, the working syntax for the token is:
and not
The latter is consistent with the GitHub status plugin.
Keeping it
authorizationwas my oversight in #13. I am sorry for delivering broken code.In the GithubStatus plugin the
authorizationkey's value is copied as-is into the HTTP headerAuthorization. Thetokenprefix will not be split away.For the new GiteaStatus plugin the value is appended to the URI in the query parameter
?token=. Therefore I argue thattokendoesn't change terminology in the context of Gitea. Of course the final decision is up to you.Another GiteaStatus plugin got merged: https://github.com/NixOS/hydra/pull/904