My Token is not being seen. I did create one with the name cut and pasted so it should be right. (tried it several times). I tried adding some environmental secrets and variables with it and that did not work either.
Seems like adding something as an environmental variable for the mkdocs-git-commiters-apikey is a good option as well but I don’t know how to set the location. I tried adding it and just see if it worked, and it didn’t.
In another post though the author actually said environmental secret, so I am even more lost.
And I do not have a key of any kind up there right now. so that 60 person api limit is not valid on a local build I guess.
If I take the --strict limitation off I am guessing it will just add 60 people each time it compiles. so eventually they will all get downloaded. Then I can add the --strict back?
You can make unauthenticated requests if you are only fetching public data. Unauthenticated requests are associated with the originating IP address, not with the user or application that made the request.
The primary rate limit for unauthenticated requests is 60 requests per hour."
It will work without the token, but it will be unreliable in getting the data correct
That is odd, then that is not the issue here. It just stops at 5 co-author errors. I have done over 60 attempts so the mkdocs key must be okay for that part.
So now the issue is why can’t I get the co authors, I need to change a permission in the key it IS using. What key is it using??
“For a repository hosted on GitHub, you can provide a token to increase the rate limit and go beyond the default 60 requests per hour per IP address. The plugin will make one request per mkdocs document.”
If you aren’t setting a token, it is making an anonymous request, and should be subject to the limit.
Your best best is probably to go ahead and make the token as it needs.
Create a secret in github that you can use in your Workflow
Add your secret as an environment variable, then set up the mkdocs.yml to use that environment variable
First, I would create the token, and verify the errors go away using the token in a local build to make it easier to verify the first step before trying to automate it
For private GitHub repositories, you only need to allow read-only access to Contents and Metadata on the target repository. This could be done by setting Read-only access of Permissions > Repository permissions > Contents.
This action supports building and deploying with a GITHUB_TOKEN. This token is automatically generated by Github Actions when a workflow runs so it is convenient.
It is more secure than a personal token, since you never actually see the value of the GITHUB_TOKEN and also the GITHUB_TOKEN is scoped to only work for a single repo.
You may need to give the GITHUB_TOKEN write permission. Go to your repository’s Settings > Actions > General > Workflow Permissions and select Read and write permissions.
Note that for this approach, Github Pages will be enabled in Settings but you will not have a URL displayed or environment tab yet. So change the Github Pages settings to another target and then back again to gh-pages (if that is your branch to serve) - then you will see a URL. This step is only needed on the first deploy and no action is needed later on."
