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
"text": "# Workflow based on the main w3c/spec-prod action example:\n# https://github.com/w3c/spec-prod/#basic-usage\n#\n# Custom code added to generate the CDDL messages appendix for inclusion in the\n# generated specification file.\n\nname: Build, Validate, and Deploy\n\non:\n # Worflow runs on pull requests where it makes sure that the spec can still be\n # generated, that markup is valid and that there are no broken links, as\n # well as on pushes to the default branch where it also deploys the generated\n # spec to the gh-pages branch. The \"workflow_dispatch\" hook allows admins to\n # also trigger the workflow manually from GitHub's UI.\n pull_request: {}\n push:\n branches: [main]\n workflow_dispatch:\n\njobs:\n main:\n runs-on: ubuntu-latest\n steps:\n # See doc at https://github.com/actions/checkout/\n - name: Checkout repository\n uses: actions/checkout@v4\n\n # See doc at https://github.com/actions/setup-python/\n - name: Setup Python\n uses: actions/setup-python@v5\n with:\n python-version: 3.9\n\n - name: Install Python dependencies\n run: |\n python -m pip install --upgrade pip\n pip install Pygments\n\n # Note: the step actually generates all CDDL message pages, but the\n # w3c/spec-prod action cleans these files after each build, so we'll\n # have to generate them again each time.\n - name: Generate messages_appendix.html\n run: python scripts/pygmentize_dir.py\n\n # See doc at https://github.com/w3c/spec-prod/#spec-prod\n # The action only deploys the generated spec to the gh-pages branch when\n # the workflow was triggered by a push to the default branch.\n - name: Build and validate index.html, push to gh-pages branch if needed\n uses: w3c/spec-prod@v2\n with:\n GH_PAGES_BRANCH: gh-pages\n W3C_ECHIDNA_TOKEN: ${{ secrets.ECHIDNA_TOKEN }}\n W3C_WG_DECISION_URL: https://lists.w3.org/Archives/Public/public-secondscreen/2022Apr/0007.html\n W3C_BUILD_OVERRIDE: |\n status: WD\n\n - name: Generate application_messages.html\n run: python scripts/pygmentize_dir.py\n\n - name: Build and validate application.html, push to gh-pages branch if needed\n uses: w3c/spec-prod@v2\n with:\n SOURCE: application.bs\n TOOLCHAIN: bikeshed\n GH_PAGES_BRANCH: gh-pages\n W3C_ECHIDNA_TOKEN: ${{ secrets.ECHIDNA_TOKEN_APPLICATION }}\n\n - name: Generate network_messages.html\n run: python scripts/pygmentize_dir.py\n\n - name: Build and validate network.html, push to gh-pages branch if needed\n uses: w3c/spec-prod@v2\n with:\n SOURCE: network.bs\n TOOLCHAIN: bikeshed\n GH_PAGES_BRANCH: gh-pages\n W3C_ECHIDNA_TOKEN: ${{ secrets.ECHIDNA_TOKEN_NETWORK }}\n"
81559
+
"text": "# Workflow based on the main w3c/spec-prod action example:\n# https://github.com/w3c/spec-prod/#basic-usage\n#\n# Custom code added to generate the CDDL messages appendix for inclusion in the\n# generated specification file.\n\nname: Build, Validate, and Deploy\n\non:\n # Worflow runs on pull requests where it makes sure that the spec can still be\n # generated, that markup is valid and that there are no broken links, as\n # well as on pushes to the default branch where it also deploys the generated\n # spec to the gh-pages branch. The \"workflow_dispatch\" hook allows admins to\n # also trigger the workflow manually from GitHub's UI.\n pull_request: {}\n push:\n branches: [main]\n workflow_dispatch:\n\njobs:\n main:\n runs-on: ubuntu-latest\n steps:\n # See doc at https://github.com/actions/checkout/\n - name: Checkout repository\n uses: actions/checkout@v4\n\n # See doc at https://github.com/actions/setup-python/\n - name: Setup Python\n uses: actions/setup-python@v5\n with:\n python-version: 3.9\n\n - name: Install Python dependencies\n run: |\n python -m pip install --upgrade pip\n pip install Pygments\n\n # Note: the step actually generates all CDDL message pages, but the\n # w3c/spec-prod action cleans these files after each build, so we'll\n # have to generate them again each time.\n - name: Generate messages_appendix.html\n run: python scripts/pygmentize_dir.py\n\n # See doc at https://github.com/w3c/spec-prod/#spec-prod\n # The action only deploys the generated spec to the gh-pages branch when\n # the workflow was triggered by a push to the default branch.\n - name: Build and validate index.html, push to gh-pages branch if needed\n uses: w3c/spec-prod@v2\n with:\n GH_PAGES_BRANCH: gh-pages\n\n - name: Generate application_messages.html\n run: python scripts/pygmentize_dir.py\n\n - name: Build and validate application.html, push to gh-pages branch if needed\n uses: w3c/spec-prod@v2\n with:\n SOURCE: application.bs\n TOOLCHAIN: bikeshed\n GH_PAGES_BRANCH: gh-pages\n W3C_ECHIDNA_TOKEN: ${{ secrets.ECHIDNA_TOKEN_APPLICATION }}\n\n - name: Generate network_messages.html\n run: python scripts/pygmentize_dir.py\n\n - name: Build and validate network.html, push to gh-pages branch if needed\n uses: w3c/spec-prod@v2\n with:\n SOURCE: network.bs\n TOOLCHAIN: bikeshed\n GH_PAGES_BRANCH: gh-pages\n W3C_ECHIDNA_TOKEN: ${{ secrets.ECHIDNA_TOKEN_NETWORK }}\n"
81512
81560
},
81513
81561
"travis": null,
81514
81562
"contributing": {
@@ -100616,7 +100664,7 @@
100616
100664
"body": "# Code of Conduct\n\nAll documentation, code, communication and discussion in this repository are covered by the [W3C Code of Conduct](https://www.w3.org/policies/code-of-conduct/).\n"
100617
100665
},
100618
100666
"readme": {
100619
-
"text": "# W3C Security Interest Group\n\nThis GitHub repository serves the [W3C Security Interest Group](https://www.w3.org/groups/ig/security/). \n\n# Security Reviews\n\n* **Do you need a security review?** Open an [issue in the w3c/security-request repository](https://github.com/w3c/security-request/issues/new/choose)\n* **Would you like to do a security review?** Join us ([how to contribute](CONTRIBUTING.md)), read the [how to review](https://github.com/w3c/securityig/blob/main/administration/how-to-review.md), and look at our [backlog](https://github.com/w3c/security-request/issues)\n* Thanks our [Security Reviewers](https://www.w3.org/PM/horizontal/leaderboard.html?repo=Security)\n \n# Administration\n\n* [Administration](https://github.com/w3c/securityig/administration)\n* [Meetings](https://github.com/w3c/securityig/meetings)\n\n# Tools \n\n* [Chair Dashboard](https://www.w3.org/PM/Groups/chairboard.html?gid=ig/security)\n* [Horizontal Dashboard](https://www.w3.org/PM/horizontal/board.html?name=Security)\n* [Comment Tracker](https://www.w3.org/PM/horizontal/?repo=w3c/security-review)\n\n# Pages\n* [Contribution guidelines](CONTRIBUTING.md)\n* [Governance and roles](GOVERNANCE.md)\n* [Code of Conduct](CODE_OF_CONDUCT.md)\n\n<!--\n\n**Here are some ideas to get you started:**\n\n🙋♀️ A short introduction - what is your organization all about?\n🌈 Contribution guidelines - how can the community get involved?\n👩💻 Useful resources - where can the community find your docs? Is there anything else the community should know?\n🍿 Fun facts - what does your team eat for breakfast?\n🧙 Remember, you can do mighty things with the power of [Markdown](https://docs.github.com/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)\n-->\n"
100667
+
"text": "# W3C Security Interest Group\n\nThis GitHub repository serves the [W3C Security Interest Group](https://www.w3.org/groups/ig/security/). \n\n# Security Reviews\n\n* **Do you need a security review?** Open an [issue in the w3c/security-request repository](https://github.com/w3c/security-request/issues/new/choose)\n* **Would you like to do a security review?** Join us ([how to contribute](CONTRIBUTING.md)), read the [how to review](https://github.com/w3c/securityig/blob/main/administration/how-to-review.md), and look at our [backlog](https://github.com/w3c/security-request/issues)\n* Thanks our [Security Reviewers](https://www.w3.org/PM/horizontal/leaderboard.html?repo=Security)\n \n# Administration\n\n* [Administration](https://github.com/w3c/securityig/administration)\n* [Meetings](https://github.com/w3c/securityig/meetings)\n\n# Tools \n* [Chair Dashboard](https://www.w3.org/PM/Groups/chairboard.html?gid=ig/security)\n* [Horizontal Dashboard](https://www.w3.org/PM/horizontal/board.html?name=Security)\n* [Comment Tracker](https://www.w3.org/PM/horizontal/?repo=w3c/security-review)\n* [Review Dashboard with a view issues for each Spec](https://www.w3.org/PM/horizontal/reviews.html)\n\n\n# Pages\n* [Contribution guidelines](CONTRIBUTING.md)\n* [Governance and roles](GOVERNANCE.md)\n* [Code of Conduct](CODE_OF_CONDUCT.md)\n\n<!--\n\n**Here are some ideas to get you started:**\n\n🙋♀️ A short introduction - what is your organization all about?\n🌈 Contribution guidelines - how can the community get involved?\n👩💻 Useful resources - where can the community find your docs? Is there anything else the community should know?\n🍿 Fun facts - what does your team eat for breakfast?\n🧙 Remember, you can do mighty things with the power of [Markdown](https://docs.github.com/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)\n-->\n"
100620
100668
},
100621
100669
"w3c": {
100622
100670
"group": [
@@ -142400,6 +142448,14 @@
142400
142448
"isPrivate": false,
142401
142449
"createdAt": "2024-06-27T22:52:23Z",
142402
142450
"labels": [
142451
+
{
142452
+
"name": "a11y-needs-resolution",
142453
+
"color": "ea7472"
142454
+
},
142455
+
{
142456
+
"name": "a11y-tracker",
142457
+
"color": "ea7472"
142458
+
},
142403
142459
{
142404
142460
"name": "bug",
142405
142461
"color": "d73a4a"
@@ -142424,14 +142480,38 @@
142424
142480
"name": "help wanted",
142425
142481
"color": "008672"
142426
142482
},
142483
+
{
142484
+
"name": "i18n-needs-resolution",
142485
+
"color": "F9C9FF"
142486
+
},
142487
+
{
142488
+
"name": "i18n-tracker",
142489
+
"color": "F9C9FF"
142490
+
},
142427
142491
{
142428
142492
"name": "invalid",
142429
142493
"color": "e4e669"
142430
142494
},
142495
+
{
142496
+
"name": "privacy-needs-resolution",
142497
+
"color": "d4af37"
142498
+
},
142499
+
{
142500
+
"name": "privacy-tracker",
142501
+
"color": "d4af37"
142502
+
},
142431
142503
{
142432
142504
"name": "question",
142433
142505
"color": "d876e3"
142434
142506
},
142507
+
{
142508
+
"name": "tag-needs-resolution",
142509
+
"color": "7fff00"
142510
+
},
142511
+
{
142512
+
"name": "tag-tracker",
142513
+
"color": "7fff00"
142514
+
},
142435
142515
{
142436
142516
"name": "wontfix",
142437
142517
"color": "ffffff"
@@ -159698,6 +159778,14 @@
159698
159778
"name": "Status: PR in review",
159699
159779
"color": "58C8FA"
159700
159780
},
159781
+
{
159782
+
"name": "tag-needs-resolution",
159783
+
"color": "7fff00"
159784
+
},
159785
+
{
159786
+
"name": "tag-tracker",
159787
+
"color": "7fff00"
159788
+
},
159701
159789
{
159702
159790
"name": "tc39-tracker",
159703
159791
"color": "FBCA04"
@@ -161122,7 +161210,7 @@
161122
161210
"license": null,
161123
161211
"codeOfConduct": null,
161124
161212
"readme": {
161125
-
"text": "# Web Platform Gaps\n\nWhat are the big unmet user needs of the web platform?\n\nContent in [Issues](issues/).\n"
161213
+
"text": "# Web Platform Gaps\n\nWhat are the big unmet user needs of the web platform?\n\nContent in [Issues](https://github.com/w3ctag/gaps/issues).\n"
0 commit comments