Merge branch 'main' into smockle/results

Author: smockle

.github/actions/file/src/Issue.ts

@@ -1,50 +1,63 @@
 import type { Issue as IssueInput } from "./types.d.js";
 
 export class Issue implements IssueInput {
-  /**
-   * Extracts owner, repository, and issue number from a GitHub issue URL.
-   * @param issueUrl A GitHub issue URL (e.g. `https://github.com/owner/repo/issues/42`).
-   * @returns An object with `owner`, `repository`, and `issueNumber` keys.
-   * @throws The provided URL is unparseable due to its unexpected format.
-   */
-  static parseIssueUrl(issueUrl: string): {
+  #url!: string;
+  #parsedUrl!: {
     owner: string;
     repository: string;
     issueNumber: number;
-  } {
-    const { owner, repository, issueNumber } =
-      /\/(?<owner>[^/]+)\/(?<repository>[^/]+)\/issues\/(?<issueNumber>\d+)(?:[/?#]|$)/.exec(
-        issueUrl
-      )?.groups || {};
-    if (!owner || !repository || !issueNumber) {
-      throw new Error(`Could not parse issue URL: ${issueUrl}`);
-    }
-    return { owner, repository, issueNumber: Number(issueNumber) };
-  }
-
-  url: string;
+  };
   nodeId: string;
   id: number;
   title: string;
   state?: "open" | "reopened" | "closed";
 
+  constructor({ url, nodeId, id, title, state }: IssueInput) {
+    this.url = url;
+    this.nodeId = nodeId;
+    this.id = id;
+    this.title = title;
+    this.state = state;
+  }
+
+  set url(newUrl: string) {
+    this.#url = newUrl;
+    this.#parsedUrl = this.#parseUrl();
+  }
+
+  get url(): string {
+    return this.#url;
+  }
+
   get owner(): string {
-    return Issue.parseIssueUrl(this.url).owner;
+    return this.#parsedUrl.owner;
   }
 
   get repository(): string {
-    return Issue.parseIssueUrl(this.url).repository;
+    return this.#parsedUrl.repository;
   }
 
   get issueNumber(): number {
-    return Issue.parseIssueUrl(this.url).issueNumber;
+    return this.#parsedUrl.issueNumber;
   }
 
-  constructor({ url, nodeId, id, title, state }: IssueInput) {
-    this.url = url;
-    this.nodeId = nodeId;
-    this.id = id;
-    this.title = title;
-    this.state = state;
+  /**
+   * Extracts owner, repository, and issue number from the Issue instance’s GitHub issue URL.
+   * @returns An object with `owner`, `repository`, and `issueNumber` keys.
+   * @throws The provided URL is unparseable due to its unexpected format.
+   */
+  #parseUrl(): {
+    owner: string;
+    repository: string;
+    issueNumber: number;
+  } {
+    const { owner, repository, issueNumber } =
+      /\/(?<owner>[^/]+)\/(?<repository>[^/]+)\/issues\/(?<issueNumber>\d+)(?:[/?#]|$)/.exec(
+        this.#url
+      )?.groups || {};
+    if (!owner || !repository || !issueNumber) {
+      throw new Error(`Could not parse issue URL: ${this.#url}`);
+    }
+    return { owner, repository, issueNumber: Number(issueNumber) };
   }
 }

.github/workflows/test.yml

@@ -74,7 +74,7 @@ jobs:
           login_url: http://127.0.0.1:4000/
           username: ${{ secrets.TEST_USERNAME }}
           password: ${{ secrets.TEST_PASSWORD }}
-          repository: github-community-projects/continuous-ai-for-accessibility-scanner
+          repository: github-community-projects/continuous-ai-for-accessibility-scanner-testing
           token: ${{ secrets.GH_TOKEN }}
           cache_key: ${{ steps.cache_key.outputs.cache_key }}
 
@@ -89,7 +89,7 @@ jobs:
           npm ci
           npm run test
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
           CACHE_PATH: ${{ steps.cache_key.outputs.cache_key }}
 
       - name: Clean up issues and pull requests
@@ -118,7 +118,7 @@ jobs:
                 fi
               done
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
 
       - name: Clean up cached results
         if: ${{ always() }}

CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at <[email protected]>. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [https://www.contributor-covenant.org/version/1/4/code-of-conduct/][version]
+
+[homepage]: https://www.contributor-covenant.org
+[version]: https://www.contributor-covenant.org/version/1/4/code-of-conduct/

CONTRIBUTING.md

@@ -0,0 +1,21 @@
+## Contributing
+
+[fork]: https://github.com/github-community-projects/continuous-ai-for-accessibility-scanner/fork
+[pr]: https://github.com/github-community-projects/continuous-ai-for-accessibility-scanner/compare
+
+Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.
+
+Contributions to this project are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the [project's open source license](LICENSE).
+
+Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
+
+## Submitting a pull request
+
+Thank you for your interest in this GitHub action, however, right now we are not taking contributions.
+
+
+## Resources
+
+- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
+- [Using Pull Requests](https://help.github.com/articles/about-pull-requests/)
+- [GitHub Support](https://support.github.com)

README.md

@@ -12,6 +12,11 @@ The a11y scanner helps teams:
 
 ---
 
+## Requirements
+
+This project is a GitHub Actions action. A GitHub Actions workflow is required to run it, and you must have available GitHub Actions minutes.
+
+📚 [Understanding GitHub Actions](https://docs.github.com/en/actions/get-started/understand-github-actions) | [Quickstart for GitHub Actions](https://docs.github.com/en/actions/get-started/quickstart) | [Writing workflows](https://docs.github.com/en/actions/how-tos/write-workflows) | [GitHub Actions billing](https://docs.github.com/en/billing/concepts/product-billing/github-actions)
 ## Getting Started
 
 ### 1. Add a Workflow File
@@ -26,23 +31,13 @@ jobs:
   accessibility_scanner:
     runs-on: ubuntu-latest
     steps:
-      # Retrieve the scanner code
-      - uses: actions/checkout@v5
-        with:
-          repository: github-community-projects/continuous-ai-for-accessibility-scanner
-          ref: v1
-          token: ${{ secrets.GH_COMMUNITY_PROJECTS_TOKEN }} # This token must have read access to github-community-projects/continuous-ai-for-accessibility-scanner; more information below.
-          path: ./.github/actions/continuous-ai-for-accessibility-scanner
-      # Prepare the scanner to run
-      - shell: bash
-        run: cp -Rf ./.github/actions/continuous-ai-for-accessibility-scanner/.github/actions/* ./.github/actions
-      # Run the scanner
-      - uses: ./.github/actions/continuous-ai-for-accessibility-scanner
+      - uses: github-community-projects/continuous-ai-for-accessibility-scanner@v1
         with:
           urls: | # Provide a newline-delimited list of URLs to scan; more information below.
             REPLACE_THIS
           repository: REPLACE_THIS/REPLACE_THIS # Provide a repository name-with-owner (in the format "primer/primer-docs"). This is where issues will be filed and where Copilot will open PRs; more information below.
           token: ${{ secrets.GH_TOKEN }} # This token must have write access to the repo above (contents, issues, and PRs); more information below. Note: GitHub Actions’ `GITHUB_TOKEN` (https://docs.github.com/en/actions/tutorials/authenticate-with-github_token) cannot be used here.
+          cache_key: REPLACE_THIS # Provide a filename that will be used when caching results. We recommend including the name or domain of the site being scanning.
 ```
 
 > 👉 Update all `REPLACE_THIS` placeholders with your actual values. See [Action Inputs](#action-inputs) for details.
@@ -56,15 +51,9 @@ Required Permissions:
 
 ---
 
-### 2. Create Tokens and Add Secrets
-
-The a11y scanner requires two Personal Access Tokens (PATs) as repository secrets:
+### 2. Create a Token and Add a Secret
 
-#### The `GH_COMMUNITY_PROJECTS_TOKEN` is a fine-grained PAT with
-
-- `contents: read`
-- `metadata: read`
-- Scope: [`github-community-projects/continuous-ai-for-accessibility-scanner`](https://github.com/github-community-projects/continuous-ai-for-accessibility-scanner)
+The a11y scanner requires a Personal Access Token (PAT) as repository secret:
 
 #### The `GH_TOKEN` is a fine-grained PAT with
 
@@ -73,7 +62,7 @@ The a11y scanner requires two Personal Access Tokens (PATs) as repository secret
 - `issues: write`
 - `pull-requests: write`
 - `metadata: read`
-- Scope: Your target repository (where issues and PRs will be created)
+- Scope: Your target repository (where issues and PRs will be created) and the repository containing your workflow
 
 > 👉 GitHub Actions' default `GITHUB_TOKEN` cannot be used here.
 
@@ -129,8 +118,24 @@ The a11y scanner leverages Copilot coding agent, which can be configured with cu
 
 ## Feedback
 
-Beta participants have direct contact for questions and suggestions. A public feedback form will be available once the project is open-sourced.
+Please refer to the [CONTRIBUTING](./CONTRIBUTING.md) file for more information.
+
+## License 
+
+This project is licensed under the terms of the MIT open source license. Please refer to the [LICENSE](./LICENSE) file for the full terms.
+
+## Maintainers 
+
+Please refer to the [CODEOWNERS](./.github/CODEOWNERS) file for more information.
+
+## Support
+
+Please refer to the [SUPPORT](./SUPPORT.md) file for more information.
+
+## Acknowledgement
+
+Thank you to our beta testers for their help in testing this project.
 
 ---
 
-*Last updated: 2025-10-01*
+*Last updated: 2025-10-09*

SECURITY.md

@@ -0,0 +1,31 @@
+Thanks for helping make GitHub safe for everyone.
+
+# Security
+
+GitHub takes the security of our software products and services seriously, including all of the open source code repositories managed through our GitHub organizations, such as [GitHub](https://github.com/GitHub).
+
+Even though [open source repositories are outside of the scope of our bug bounty program](https://bounty.github.com/index.html#scope) and therefore not eligible for bounty rewards, we will ensure that your finding gets passed along to the appropriate maintainers for remediation. 
+
+## Reporting Security Issues
+
+If you believe you have found a security vulnerability in any GitHub-owned repository, please report it to us through coordinated disclosure.
+
+**Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.**
+
+Instead, please send an email to opensource-security[@]github.com.
+
+Please include as much of the information listed below as you can to help us better understand and resolve the issue:
+
+  * The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
+  * Full paths of source file(s) related to the manifestation of the issue
+  * The location of the affected source code (tag/branch/commit or direct URL)
+  * Any special configuration required to reproduce the issue
+  * Step-by-step instructions to reproduce the issue
+  * Proof-of-concept or exploit code (if possible)
+  * Impact of the issue, including how an attacker might exploit the issue
+
+This information will help us triage your report more quickly.
+
+## Policy
+
+See [GitHub's Safe Harbor Policy](https://docs.github.com/en/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor#1-safe-harbor-terms)

SUPPORT.md

@@ -0,0 +1,19 @@
+# Support
+
+## How to file issues and get help
+
+This project uses GitHub Issues to track bugs and feature requests. Please search the existing issues before filing new issues to avoid duplicates. For new issues, file your bug or feature request as a new issue.
+
+For help or questions about using this project, please open an issue for support requests, usage questions, or general inquiries. At this time, GitHub Discussions are not enabled. All communication should occur via issues.
+
+## Project Maintenance Status
+
+This repo `continuous-ai-for-accessibility-scanner` is under active development and maintained by GitHub staff during the public preview state. We will do our best to respond to support, feature requests, and community questions in a timely manner.
+
+## Important Notice
+
+This project is a work in progress, and we do not guarantee that code fixes or suggestions produced by Copilot will be fully accessible. Please use caution when applying the suggestions it provides. Always confirm or verify Copilot's recommendations with an accessibility subject matter expert before using them in production.
+
+## GitHub Support Policy
+
+Support for this project is limited to the resources listed above (GitHub Issues).

sites/site-with-errors/Gemfile.lock

@@ -101,7 +101,7 @@ GEM
     public_suffix (6.0.2)
     puma (7.0.4)
       nio4r (~> 2.0)
-    rack (3.2.2)
+    rack (3.2.3)
     rake (13.3.0)
     rb-fsevent (0.11.2)
     rb-inotify (0.11.1)