Add tracking labels to issue generation (#16)

This pull request exposes the `id` (e.g., `button-name`) and
`scannerType` (e.g., `axe`) for each violation, making them available to
label new issues.

By adding these labels to issues, we can effectively track both issues
and Copilot PRs, which will help us enhance our issue descriptions over
time.

Author: kendallgassner

.github/actions/file/src/openIssueForFinding.ts

@@ -16,6 +16,9 @@ export async function openIssueForFinding(octokit: Octokit, repoWithOwner: strin
       state: 'open'
     });
   } else {
+    
+    const labels = [`${finding.scannerType} rule: ${finding.ruleId}`, `${finding.scannerType}-scanning-issue`];
+
     // Otherwise, create a new issue
     const title = `Accessibility issue: ${finding.problemShort[0].toUpperCase() + finding.problemShort.slice(1)} on ${new URL(finding.url).pathname}`;
     const solutionLong = finding.solutionLong
@@ -39,7 +42,8 @@ ${solutionLong ? `\nSpecifically:\n\n${solutionLong}` : ''}
       owner,
       repo,
       title,
-      body
+      body,
+      labels
     });
   }
 }

.github/actions/file/src/types.d.ts

@@ -1,4 +1,6 @@
 export type Finding = {
+  scannerType: string;
+  ruleId: string;
   url: string;
   html: string;
   problemShort: string;

.github/actions/find/src/findForUrl.ts

@@ -12,10 +12,12 @@ export async function findForUrl(url: string): Promise<Finding[]> {
   try {
     const rawFindings = await new AxeBuilder({ page }).analyze();
     findings = rawFindings.violations.map(violation => ({
+      scannerType: 'axe',
       url,
       html: violation.nodes[0].html,
       problemShort: violation.help.toLowerCase(),
       problemUrl: violation.helpUrl,
+      ruleId: violation.id,
       solutionShort: violation.description.toLowerCase(),
       solutionLong: violation.nodes[0].failureSummary
     }));