-
Notifications
You must be signed in to change notification settings - Fork 31
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
Issues using Sample Site Template #83
Comments
I've updated the ReadMe to reflect the change in Notion UI for connecting integrations. |
Not as far as I can tell. As a test, I unpublished one of our test sites just now and docu-notion accessed it without problems. |
@JustSleightly can you try the latest (i.e. using |
@hatton Thanks for your quick update! I did notice, however, that multi-column layouts did not seem to be working like your sample site Attempting to update the sample site repository/action (by replacing the version number in the package.json to v0.15.0) did not seem to work, despite confirming all my repository secrets are correct. Perhaps the issues I've been having (other than the multi-column layout) are only specific to the sample site template? |
oh yeah this is because you need to include the CSS from the repo manually |
Hello! This is my first time attempting to use docu-notion, and docusaurus in general, so please forgive me if I may be missing anything obvious.
What I've done
I created a repository using the docu-notion-sample-site template, skipping steps 4 and 5 for testing locally as I just wanted to see if I could get this up and running first.
I've duplicated the Notion sample site without making any personal customizations to it.
I've set my repository settings to configure the GitHub Pages Build and deployment Source to GitHub Actions.
I've tested setting the
url
field (line 11) indocusaurus.config.js
to both my github username and the original one, as it wasn't specified in the README of the sample site template, but seemed off.Issues
The farthest I've gotten in the process is to the
Deploy to gh-pages
step in the action.This step returns
Permission to repository/docu-notion-test.git denied to github-actions[bot].
Log: https://github.com/JustSleightly/docu-notion-test/actions/runs/6322938490/job/17169500962
This is only after setting the github repo visibility to public, as before that I got just as far but
Write access to repository not granted
instead. Is my docu-notion repository required to be public?Log: https://github.com/JustSleightly/docu-notion-test/actions/runs/6322758127/job/17168975276
This seems to use the
GITHUB_TOKEN
instead of my Fine-grained personal access token, so it doesn't seem to be an issue with my token scope.Prior to that, I was running into an error during the
Pull from Notion
step in the action.This step returned
Error: Notion page not found "6c46c1230f914d3080dca0bc2847af57"
This issue seems similar to Notion page not found #57 which was previously closed by OP, but in my case I haven't changed the sample site.
I got past this error only by publishing my notion page publicly to the web. Is my docu-notion site required to be public?
I don't see the same "Share" option to Invite my Notion Integration like your screenshot, and was only able to add the connection using these steps in Notion's documentation
Log: https://github.com/JustSleightly/docu-notion-test/actions/runs/6322476314/job/17168173721
Lastly, every other build run seems to sporadically encounter
UnknownHTTPResponseError: Request to Notion API failed with status: 502
during thePull from Notion
step.From google results, this one seems like it may just be a Notion API issue that began reoccurring recently.
Log: https://github.com/JustSleightly/docu-notion-test/actions/runs/6322846245/job/17169220332
The text was updated successfully, but these errors were encountered: