Skip to content

🔄 synced file(s) with OrrisTech/.github#1

Open
iamzifei wants to merge 5 commits intomainfrom
repo-sync/github/default
Open

🔄 synced file(s) with OrrisTech/.github#1
iamzifei wants to merge 5 commits intomainfrom
repo-sync/github/default

Conversation

@iamzifei
Copy link
Contributor

@iamzifei iamzifei commented Feb 20, 2026

synced local file(s) with OrrisTech/.github.

This PR was automatically created by the org file sync workflow. It syncs the latest org standard files from the .github repo. Review the changes and merge when ready.

Changed files
  • created local .claude/org-rules.md from remote sync/.claude/org-rules.md
  • created local .github/pull_request_template.md from remote sync/.github/pull_request_template.md
  • created local .github/workflows/ci.yml from remote sync/.github/workflows/ci.yml
  • created local lefthook.yml from remote sync/lefthook.yml
  • created local .vscode/settings.json from remote sync/.vscode/settings.json

This PR was created automatically by the repo-file-sync-action workflow run #22209578770

Copilot AI review requested due to automatic review settings February 20, 2026 02:06
@vercel
Copy link

vercel bot commented Feb 20, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
agent-otp-website Error Error Feb 20, 2026 3:04am

Request Review

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 syncs organization-wide standard files from the OrrisTech/.github repository to ensure consistency across all repositories in the organization. The sync includes developer tooling configurations, CI/CD workflows, documentation templates, and coding guidelines.

Changes:

  • Added organizational coding rules and best practices documentation (.claude/org-rules.md)
  • Added standardized PR template with comprehensive checklists (.github/pull_request_template.md)
  • Added centralized CI workflow that calls reusable workflows from the org repo (.github/workflows/ci.yml)
  • Added git hooks configuration for pre-commit linting, typechecking, and testing (lefthook.yml)
  • Added standardized VSCode editor settings for consistent development experience (.vscode/settings.json)

Reviewed changes

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

Show a summary per file
File Description
.claude/org-rules.md Comprehensive organizational coding standards covering testing, React best practices, UI/design standards, SEO requirements, and security guidelines
.github/pull_request_template.md Standardized PR template with checklists for code quality, testing, security, documentation, UI/design, SEO, and blog content
.github/workflows/ci.yml Thin CI workflow that delegates to reusable workflows in the org repo for linting, testing, building, security audits, and React Doctor
lefthook.yml Pre-commit hooks configuration that runs linting, type checking, and related tests on staged files with support for pnpm, bun, and npm
.vscode/settings.json VSCode workspace settings for editor configuration, ESLint, TypeScript, Tailwind CSS IntelliSense, and search exclusions

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

"editor.tabSize": 2,
"editor.insertSpaces": true,
"editor.formatOnSave": true,
"editor.defaultFormatter": "esbenp.prettier-vscode",
Copy link

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

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

The VSCode settings specify Prettier as the default formatter, but Prettier is not installed as a dependency in this repository. This configuration will not work for developers unless they have Prettier installed globally. Consider either adding Prettier as a dev dependency to the root package.json, or updating the formatter settings to match the actual formatting tools used in this repository (ESLint, Biome, or none).

Copilot uses AI. Check for mistakes.
- [ ] Inline comments for complex logic only

### UI / Design (if applicable)
- [ ] Follows design system (shadcn/ui + Tailwind CSS v4)
Copy link

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

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

The pull request template references "Tailwind CSS v4" but this repository currently uses Tailwind CSS v3.4.17 (as seen in apps/website/package.json:56). This creates confusion for developers following the checklist. Update the reference to "Tailwind CSS v3" or remove the version number to avoid misleading developers about which version to use.

Suggested change
- [ ] Follows design system (shadcn/ui + Tailwind CSS v4)
- [ ] Follows design system (shadcn/ui + Tailwind CSS)

Copilot uses AI. Check for mistakes.
Comment on lines +15 to +17
- [ ] Lint passes (`pnpm lint` / `npm run lint`)
- [ ] TypeScript compiles (`pnpm typecheck` / `npm run typecheck`)
- [ ] Build succeeds (`pnpm build` / `npm run build`)
Copy link

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

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

The checklist references "pnpm lint / npm run lint" and "pnpm typecheck / npm run typecheck" and "pnpm build / npm run build", but this repository uses Bun as its package manager (packageManager: "bun@1.1.42" in package.json). For consistency and accuracy, these should reference "bun run lint", "bun run typecheck", and "bun run build" instead, or provide all three options including bun.

Suggested change
- [ ] Lint passes (`pnpm lint` / `npm run lint`)
- [ ] TypeScript compiles (`pnpm typecheck` / `npm run typecheck`)
- [ ] Build succeeds (`pnpm build` / `npm run build`)
- [ ] Lint passes (`bun run lint` / `pnpm lint` / `npm run lint`)
- [ ] TypeScript compiles (`bun run typecheck` / `pnpm typecheck` / `npm run typecheck`)
- [ ] Build succeeds (`bun run build` / `pnpm build` / `npm run build`)

Copilot uses AI. Check for mistakes.

### Component Library & Styling
- Use **shadcn/ui** components as the base component library.
- Use **Tailwind CSS v4** for all styling. No inline styles, no CSS modules, no
Copy link

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

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

The org rules document specifies "Use Tailwind CSS v4 for all styling" but this repository currently uses Tailwind CSS v3.4.17 (as seen in apps/website/package.json:56). This discrepancy creates confusion about which version developers should follow. Update this to reference Tailwind CSS v3, or update the repository's Tailwind dependency to match the org standard of v4.

Suggested change
- Use **Tailwind CSS v4** for all styling. No inline styles, no CSS modules, no
- Use **Tailwind CSS v3** for all styling. No inline styles, no CSS modules, no

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments