Skip to content
This repository has been archived by the owner on Jan 22, 2024. It is now read-only.

Handle private pages #7

Open
hectorsector opened this issue Feb 2, 2021 · 2 comments
Open

Handle private pages #7

hectorsector opened this issue Feb 2, 2021 · 2 comments

Comments

@hectorsector
Copy link
Member

In our early testing, we learned that private pages don't work well, we get the error:

HttpError: Resource not accessible by integration

We should look into whether it's possible to expand this action to tackle private pages. If not, we should reflect that in the lab instructions.

@hectorsector
Copy link
Member Author

we should reflect that in the lab instructions.

This is now reflected in the lab instructions via 4ccd959, so this doesn't need to be immediately resolved.

@mattdavis0351
Copy link

@hectorsector I ran into this yet again yesterday. As it stands right now, I don't think there is anything we can do on our side of things to fix this. The API has to change to allow integrations (actions) to work with private pages.

@hectorsector hectorsector transferred this issue from githubtraining/check-pages-action Apr 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants