Skip to content

chore: setup auto publish #312

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

Merged
merged 7 commits into from
Jul 10, 2025
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions .github/workflows/auto-publish.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
name: Node CI

on:
push:
branches:
- main
pull_request: {}

jobs:
validate-and-publish:
name: Validate and Publish
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: w3c/spec-prod@v2
with:
TOOLCHAIN: respec
VALIDATE_LINKS: false
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Internationally false?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VALIDATE_LINKS and VALIDATE_PUBRULES

VALIDATE_PUBRULES: false
GH_PAGES_BRANCH: gh-pages
W3C_API_KEY: ${{ secrets.W3C_API_KEY }}
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@simoneonofri, could you add this for us via the repo Setting? I can't seem to remember where to get this.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@marcoscaceres it was already here (probabily from you), I'lve just updated with the one from the token request (that said it was already generated).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

checked the Action log, it said that we don't need W3C_API_KEY

Suggested change
W3C_API_KEY: ${{ secrets.W3C_API_KEY }}

this is an example file which worked yesterday https://github.com/w3c/webappsec-subresource-integrity/blob/main/.github/workflows/auto-publish.yaml

jobs:
  main:
    name: Build, Validate and Deploy
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: w3c/spec-prod@v2
        with:
          W3C_ECHIDNA_TOKEN: ${{ secrets.ECHIDNA_TOKEN }}
          # Replace following with appropriate value. See options.md for details.
          W3C_WG_DECISION_URL: https://github.com/w3c/webappsec/issues/671
          # Usually, you want the following set too...
          TOOLCHAIN: bikeshed
          SOURCE: index.bs
          W3C_BUILD_OVERRIDE: |
            status: WD

W3C_ECHIDNA_TOKEN: ${{ secrets.ECHIDNA_TOKEN }}
W3C_WG_DECISION_URL: "https://lists.w3.org/Archives/Public/public-fedid-wg/2025Jun/0035.html"
W3C_NOTIFICATIONS_CC: "${{ secrets.CC }}"
W3C_BUILD_OVERRIDE: |
specStatus: WD
47 changes: 0 additions & 47 deletions .github/workflows/gh-pages.yml

This file was deleted.

Loading