You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use the default GITHUB_TOKEN to push updated docs to branch gh-pages. While the branch is properly updated, GitHub services seem not to detect those pushes as valid. As a result, even if sources are properly published, the web site is never updated.
The following gh pages action links to working alternatives as well as a tracking issue for the token permission
I didn't find any working alternative for my use case, since this seems to require a fix by GitHub. I am already using Deployment keys for other use cases, and it works ok. But I'm precisely trying to avoid the burden of creating and managing deployment keys for each GitHub Pages site.
I'm trying to use the default GITHUB_TOKEN to push updated docs to branch
gh-pages
. While the branch is properly updated, GitHub services seem not to detect those pushes as valid. As a result, even if sources are properly published, the web site is never updated.For example:
To Reproduce
Expected behavior
Commits pushed with the GITHUB_TOKEN should be as valid as those published by admins of the repo.
The text was updated successfully, but these errors were encountered: