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
The Build documentation / build / build_main_documentation (push) job is consistently failing during the "Syncing repository" step. The error occurs when attempting to determine the default branch name, resulting in "Bad credentials" errors.
Steps to reproduce the bug
Trigger the build_main_documentation job.
Observe the logs during the "Syncing repository" step.
Expected behavior
The workflow should be able to retrieve the default branch name without encountering credential issues.
Environment info
Syncing repository: huggingface/notebooks
Getting Git version info
Temporarily overriding HOME='/home/runner/work/_temp/00e62748-9940-4a4f-bbbc-eb2cda6d7ed6' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
/usr/bin/git config --global --add safe.directory /home/runner/work/datasets/datasets/notebooks
Initializing the repository
Disabling automatic garbage collection
Setting up auth
Determining the default branch
Retrieving the default branch name
Bad credentials - https://docs.github.com/rest
Waiting 20 seconds before trying again
Retrieving the default branch name
Bad credentials - https://docs.github.com/rest
Waiting 19 seconds before trying again
Retrieving the default branch name
Error: Bad credentials - https://docs.github.com/rest
The text was updated successfully, but these errors were encountered:
Describe the bug
The
Build documentation / build / build_main_documentation (push)
job is consistently failing during the "Syncing repository" step. The error occurs when attempting to determine the default branch name, resulting in "Bad credentials" errors.Steps to reproduce the bug
build_main_documentation
job.Expected behavior
The workflow should be able to retrieve the default branch name without encountering credential issues.
Environment info
The text was updated successfully, but these errors were encountered: