Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use docusaurus-bot for publishing #5221

Merged
merged 1 commit into from
Jan 3, 2018
Merged

Use docusaurus-bot for publishing #5221

merged 1 commit into from
Jan 3, 2018

Conversation

JoelMarcey
Copy link
Contributor

Summary

Use the docusaurus-bot (maybe temporarily) to unblock publishing the site until we can get the jest-bot in order.

Test plan

Try it live

@SimenB
Copy link
Member

SimenB commented Jan 3, 2018

ERROR: The key you are authenticating with has been marked as read only.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Error: Git push failed

@JoelMarcey
Copy link
Contributor Author

sigh -- I am not sure why that is. I will investigate.

@JoelMarcey
Copy link
Contributor Author

I use the docusaurus-bot for makeitopen with a similar setup - https://github.com/facebook/makeitopen/blob/master/.circleci/config.yml#L31 except that the env variable is named GITHUB_TOKEN instead of DOCUSAURUS_PUBLISH_TOKEN

@JoelMarcey
Copy link
Contributor Author

JoelMarcey commented Jan 3, 2018

I re-ran the CircleCI job and that seemed to have passed the test this time :/

@JoelMarcey
Copy link
Contributor Author

I say we give this PR a go - we won't be in any worse shape than where we are now if it indeed does not actually publish, right? I would just be more confused as to why since I personally set this personal access token up myself. :)

@SimenB What do you think?

Copy link
Member

@SimenB SimenB left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, let's try it!

@JoelMarcey JoelMarcey merged commit 96a44df into master Jan 3, 2018
@JoelMarcey
Copy link
Contributor Author

Here we go! Crossing fingers.

@SimenB SimenB deleted the docusaurus-bot branch January 3, 2018 21:25
@JoelMarcey
Copy link
Contributor Author

Looks like it failed on master :(

@SimenB
Copy link
Member

SimenB commented Jan 3, 2018

I clicked rerun with ssh, maybe it helps? Perhaps permissions are different from a "normal" build and ssh build?

@SimenB
Copy link
Member

SimenB commented Jan 3, 2018

Nope.

image

@JoelMarcey
Copy link
Contributor Author

Do you see anything technically different from:

https://github.com/facebook/makeitopen/blob/master/.circleci/config.yml#L31

to

https://github.com/facebook/jest/blob/master/.circleci/config.yml#L24

That's my only lead right now as to why this works on one and not the other

@SimenB
Copy link
Member

SimenB commented Jan 3, 2018

These are the available env vars, maybe use the docusarus one?

image

I don't know what accesses the GITHUB_TOKEN has, perhaps not push?

@JoelMarcey
Copy link
Contributor Author

I figured it out. And I am ashamed.

I forgot to give docusaurus-bot write access to the actual Jest repo itself.

@JoelMarcey
Copy link
Contributor Author

I am re-running the CircleCI build now.

@JoelMarcey
Copy link
Contributor Author

screenshot 2018-01-03 13 48 09

@JoelMarcey
Copy link
Contributor Author

I might need to create a new key after I now gave write access. Let me try that.

@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants