Testing for 2.9.0 release

[JoyceZhu]

No description provided.

[Copilot]

Pull request overview

This PR prepares version 2.9.0 for release by introducing a screenshot capture feature for accessibility scans, applying consistent code formatting across the codebase, and updating dependencies. The changes include converting the codebase to use Prettier formatting with single quotes and no semicolons, adding ESLint configuration, and implementing screenshot functionality that captures page states and stores them in a GitHub cache branch.

Changes:

• Added screenshot capture functionality with optional include_screenshots input to save and link screenshots in accessibility issues
• Applied consistent code formatting across all TypeScript files (single quotes, no semicolons, Prettier-compatible)
• Added linting and formatting tooling with ESLint 10 and Prettier 3.8, including a new lint workflow

Reviewed changes

Copilot reviewed 39 out of 50 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
package.json	Added eslint, prettier, and typescript-eslint dependencies; added lint and format scripts
eslint.config.js	New ESLint configuration using typescript-eslint recommended config with Prettier
.github/workflows/lint.yml	New workflow to run linting and format checking on PRs and main branch
action.yml	Added include_screenshots input parameter and screenshot saving step
README.md	Documented the new include_screenshots parameter
.github/actions/find/src/generateScreenshots.ts	New function to capture screenshots and save them with UUID filenames
.github/actions/find/src/findForUrl.ts	Integrated screenshot generation when enabled
.github/actions/file/src/generateIssueBody.ts	New function to generate issue body with optional screenshot links
.github/actions/file/src/openIssue.ts	Refactored to use generateIssueBody function, accepts screenshotRepo parameter
.github/actions/file/src/reopenIssue.ts	Enhanced to update issue body with latest finding and screenshot info
.github/actions/gh-cache/save/action.yml	Enhanced to support directory uploads in addition to files
All TypeScript files	Applied consistent Prettier formatting (single quotes, no semicolons)

Files not reviewed (4)

• .github/actions/auth/package-lock.json: Language not supported
• .github/actions/file/package-lock.json: Language not supported
• .github/actions/find/package-lock.json: Language not supported
• .github/actions/fix/package-lock.json: Language not supported

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The indentation in the generated issue body is inconsistent. Lines 22-25 and 29-35 have leading spaces that will appear in the rendered Markdown. This creates awkward whitespace in the GitHub issue. Consider using template literals without indentation or use a dedent function to normalize the whitespace.

Suggested change

	const acceptanceCriteria = `## Acceptance Criteria
	- [ ] The specific axe violation reported in this issue is no longer reproducible.
	- [ ] The fix MUST meet WCAG 2.1 guidelines OR the accessibility standards specified by the repository or organization.
	- [ ] A test SHOULD be added to ensure this specific axe violation does not regress.
	- [ ] This PR MUST NOT introduce any new accessibility issues or regressions.
	`
	const body = `## What
	An accessibility scan flagged the element \`${finding.html}\` on ${finding.url} because ${finding.problemShort}. Learn more about why this was flagged by visiting ${finding.problemUrl}.
	${screenshotSection ?? ''}
	To fix this, ${finding.solutionShort}.
	${solutionLong ? `\nSpecifically:\n\n${solutionLong}` : ''}
	${acceptanceCriteria}
	`
	const acceptanceCriteria = [
	'## Acceptance Criteria',
	'- [ ] The specific axe violation reported in this issue is no longer reproducible.',
	'- [ ] The fix MUST meet WCAG 2.1 guidelines OR the accessibility standards specified by the repository or organization.',
	'- [ ] A test SHOULD be added to ensure this specific axe violation does not regress.',
	'- [ ] This PR MUST NOT introduce any new accessibility issues or regressions.',
	].join('\n')
	const bodyLines = [
	'## What',
	`An accessibility scan flagged the element \`${finding.html}\` on ${finding.url} because ${finding.problemShort}. Learn more about why this was flagged by visiting ${finding.problemUrl}.`,
	'',
	screenshotSection ?? '',
	`To fix this, ${finding.solutionShort}.`,
	solutionLong ? `\nSpecifically:\n\n${solutionLong}` : '',
	'',
	acceptanceCriteria,
	]
	const body = bodyLines.join('\n')

[Copilot]

The variable screenshotSection is defined but never assigned when finding.screenshotId is falsy. When used in line 31 with the nullish coalescing operator (??), this results in outputting 'undefined' as a string in the issue body. Instead, initialize screenshotSection to an empty string or undefined explicitly.

Suggested change

	let screenshotSection
	let screenshotSection = ''