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

Web Pages and GitHub Pages Outdated since 2022-10-20 #110

Closed
bc-lee opened this issue May 30, 2024 · 1 comment
Closed

Web Pages and GitHub Pages Outdated since 2022-10-20 #110

bc-lee opened this issue May 30, 2024 · 1 comment

Comments

@bc-lee
Copy link

bc-lee commented May 30, 2024

Both the Specification and Editor's Draft web pages haven't been updated since 2022-10-20.

Additionally, the gh-pages branch on the GitHub repository hasn't been updated since the same date.

It appears that the GitHub Action .github/workflows/auto-publish.yml has never succeeded. The issue may be related to the commit efec34b. This commit updated the workflow configuration but appears to have an error.

The first few lines of the file define the workflow trigger:

name: Auto-publish
on:
  pull_request: {}
  paths: index.bs
  push:
    branches: [main]

The paths element within the top-level on section is not supported. The intended behavior seems to be triggering the workflow when the index.bs file is updated.

To correct the trigger configuration, use the paths element within the on.push section:

name: Auto-publish
on:
  pull_request:
    branches: [main]
    paths:
      - index.bs
  push:
    branches: [main]
    paths:
      - index.bs

( https://github.com/w3c/spec-prod/blob/796e4101600225fe24d1e967416e348fefdcc266/docs/examples.md#multiple-specs-in-same-repository has more examples to use paths element in on element. )

Also, I wonder if such a filtering is necessary. It seems other files may affect the generated web pages. If the intention is to update the web pages when any file is updated, the correct way is to remove paths element from on element.

@dontcallmedom
Copy link
Member

many thanks for the report, should be fixed now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants