Replies: 2 comments 1 reply
-
Thanks, I'm glad you love those! Tokens should be added via secrets. I'm not sure if readthedocs offers such a functionality, but it's the de-facto standard, supported by GitHub and GitLab. I'm looping in @ojacques, as he's the expert on the git-committers plugin. |
Beta Was this translation helpful? Give feedback.
-
Hi @rfay - glad you find it useful!
The GitHub token does not need any scope. You can uncheck everything. I just updated the docs. Regarding providing the token through a secret and an environment variable, it's standard practice, although I agree not the best security posture. |
Beta Was this translation helpful? Give feedback.
-
I'm experimenting with the very nice (insiders) contributors feature with the
git committers
plugin on insiders, and really love being able to show those.Of course it requires a GitHub token. But...
Edit: I see in https://github.com/ojacques/mkdocs-git-committers-plugin-2 that the token scope should be documented there. I imagine it requires no privs at all. I'd still love direction from experts about how to inject this safely in readthedocs. I guess a token with no scope is not that much worth worrying about.
Beta Was this translation helpful? Give feedback.
All reactions