Skip to content

Conversation

@justlevine
Copy link
Collaborator

@justlevine justlevine commented Aug 4, 2025

What

Adds a basic linting workflow

Why

Code quality is important for humans and bots. even in a POC.

Related Issue(s):

How

Testing Instructions

Screenshots

Additional Info

Checklist

  • I have read the Contribution Guidelines.
  • My code is tested to the best of my abilities.
  • My code passes all lints (PHPCS, PHPStan, ESLint, etc).
  • My code has detailed inline documentation.
  • My code has automated tests to verify it works as intended.
  • I have updated the relevant documentation (if any).

@justlevine justlevine requested a review from Copilot August 4, 2025 15:21
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds a GitHub Actions workflow for code quality checks including linting, formatting, and type checking. It also excludes WordPress code from Prettier formatting since it's handled separately.

  • Adds a comprehensive lint workflow with ESLint, Prettier, and TypeScript checks
  • Configures the workflow to run on pull requests to main and develop branches
  • Excludes WordPress directory from Prettier formatting

Reviewed Changes

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

File Description
.github/workflows/lint.yml Adds new CI workflow with three jobs for linting, formatting, and type checking
.prettierignore Excludes WordPress directory from Prettier formatting

@justlevine justlevine merged commit 10a909c into main Aug 4, 2025
7 checks passed
@justlevine justlevine deleted the ci-lints branch August 4, 2025 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants