Dear all,
I was wondering if I need to modify some site configurations after I change the name of team on Netlify.
I am suspecting this change has been a cause of build failures, somehow.
Is there a need to change anything after a team name change?
Thank you very much @Melvin . It happens that it is nothing to do with the team name change. This particular error you mentioned was about a lack of attribute in the playbook; fixed it. But…
About the build… I managed to build the documentation by sacrificing the access to an internal (private) repo of ours. Apparently, our former tech writers chose the option to create a repository secret and address it in the Netlify as an environment variable. As they are no longer with us, I am guessing the secrets are invalid. Now, I think I will try to provide my personal access token as the environment variable, and see how it goes.
So the steps in mind are:
1 - Get my personal access token and enable the SSO.
2 - Put the token information into the Netlify in the form https://<token>:@github.com
3 - Trigger deploy.
Hi @Melvin ,
I am still experiencing the issue. For now, as a workaround, I commented out the problematic content URLs in our playbook; of course this means some of the documentation features are not working.
And I was wondering where the validation between Netlify and GitHub is happening, in terms of secrets/tokens. Should I look for a config file, or some other configuration?