Move eslint-plugin-primer-react into monorepo

[Copilot]

Consolidates eslint-plugin-primer-react from its standalone repository into this monorepo as a workspace package. Development and publishing remain independent, but source now lives alongside the components it lints.

Changes

Package structure:

• Source copied to packages/eslint-plugin-primer-react/
• Preserved existing test suite, documentation, and configuration
• Updated repository URLs in package.json to reflect new location

Integration:

• Added workspace entry in root package.json
• Removed npm dependency on external package
• Modified eslint.config.mjs to import via relative path: ./packages/eslint-plugin-primer-react/src/index.js
• Added package to globalIgnores (uses CommonJS, conflicts with repo's TypeScript linting rules)

No behavioral changes - plugin rules and functionality unchanged.

Changelog

Changed

• eslint-plugin-primer-react now sourced from monorepo workspace instead of npm

Rollout strategy

• Patch release
• Minor release
• Major release; if selected, include a written rollout or migration plan
• None; internal tooling change, no API surface modified

Testing & Reviewing

Verify lint rules still function:

npm run lint        # Should pass
npm test           # All tests pass
npm run build      # Builds successfully

The plugin loads correctly from local path and enforces rules as before.

Merge checklist

• Added/updated tests
• Added/updated documentation
• Added/updated previews (Storybook)
• Changes are SSR compatible
• Tested in Chrome
• Tested in Firefox
• Tested in Safari
• Tested in Edge
• (GitHub staff only) Integration tests pass at github/github

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[changeset-bot]

⚠️ No Changeset found

Latest commit: df0a704

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR