You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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:
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.
The text was updated successfully, but these errors were encountered:
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:
The
paths
element within the top-levelon
section is not supported. The intended behavior seems to be triggering the workflow when theindex.bs
file is updated.To correct the trigger configuration, use the
paths
element within theon.push
section:( https://github.com/w3c/spec-prod/blob/796e4101600225fe24d1e967416e348fefdcc266/docs/examples.md#multiple-specs-in-same-repository has more examples to use
paths
element inon
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 fromon
element.The text was updated successfully, but these errors were encountered: