-
Notifications
You must be signed in to change notification settings - Fork 79
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
Value 'github-pages' is not valid #344
Comments
Cannot see the whole workflow in the screenshot but GitHub Pages does not really own the VS code extension anyway. Would you mind asking in https://github.com/orgs/community/discussions/categories/actions?discussions_q=is%3Aunanswered+category%3AActions? |
It would be this one https://github.com/socketry/async/blob/main/.github/workflows/documentation.yaml which I use across multiple projects. I suppose there must be a schema for this file, defined by VSCode, which doesn't take into account GitHub pages... |
I found the schema and created an issue ☝🏼 |
Add back in removed environment. Error being shown raised in GitHub Actions with this issue: actions/deploy-pages#344
Just to stress: This means that the example code from this action's README yields a linting error. |
Whoa, looks like our efforts were totally misdirected. Apparently, the GitHub Actions extension performs a lookup for existing environments in one's repo and complains about any non-existing ones, even though the workflow might run fine and just create one. |
Closing this issue because it is not actionable from that Action. |
Not sure why this happens, but looks like the schema validation in VSCode reports this error:
It's a little confusing as I believe this is actually correct.
The text was updated successfully, but these errors were encountered: