no
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
You need to create a secret and put your token in it.
You just need to replace it in the yaml.
You can’t call it GITHUB_TOKEN though.
So if you create one called ‘REMOTE_TOKEN’
it would be replaced like this instead
env:
GITHUB_TOKEN: ${{ secrets.REMOTE_TOKEN}}
ahh…
then scratch all that lol
built-in is better than self-created if it works
but you still need to put that in the action file
to define the environment variable when it runs the build command
worth a shot!
adding a second will either fail, or just overwrite the first
contributors · V1EngineeringInc/V1EngineeringInc-Docs@1b438c3 · GitHub, Nope same error. I think I need to make a new token, not use the automatic githubtoken
You may have exceeded the API rate limit or need to be authorized. You can set a token under 'token' mkdocs.yml config or MKDOCS_GIT_COMMITTERS_APIKEY environment variable.
Add another environment variable
env:
MKDOCS_GIT_COMMITTERS_APIKEY: ${{ secrets.GITHUB_TOKEN }}
GITHUB_TOKEN : ${{ secrets.GITHUB_TOKEN }}to both build and deploy?
whichever workflow is doing the mkdocs build that has the plugin fetching
ok… i see.
you have it in deploy.yml, but it should be in build.yml
that’s where the requests are actually happening, during mkdocs build
It needs it in deploy as well to be able to write I think.
it won’t hurt it to be there, but I don’t think you need it now, if you didn’t before
always been in deploy.
Running in actions
looks like it is working!!!
Badass!! Thank you.
So now I can edit the docs landing page to remove the contributors section and they will be more easily seen where they put in the work!
So I need to pack some orders but the stretch goal here is to start using the insiders edition for a few other special features.
hmm… I’ve never heard of it. Is that a MkDocs thing?
If that’s a premium/paid thing, does that affect who can contribute, or how contributions are made?
