| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
Adds ESLint coverage for the pr-checks TypeScript code and updates CI and scripts so pr-checks code is linted and tested consistently alongside the main repo.
Changes:
Copilot reviewed 7 out of 8 changed files in this pull request and generated 2 comments.
Show a summary per file| File | Description |
|---|---|
| pr-checks/sync.ts | Adds a minimal Step type and refactors string construction to be lint-friendly. |
| pr-checks/sync-back.ts | Formatting/import tweaks to satisfy lint rules. |
| pr-checks/sync-back.test.ts | Updates test text/import path and changes test registration style to satisfy linting. |
| eslint.config.mjs | Enables linting for pr-checks with the correct TS project and adjusts rules. |
| .github/workflows/pr-checks.yml | Adjusts caching and install steps; runs pr-checks tests without a local npm ci step. |
| .github/workflows/rebuild.yml | Updates script filename from sync_back.ts to sync-back.ts. |
| package.json | Adds npm workspaces configuration to include pr-checks. |
| package-lock.json | Updates lockfile to reflect workspaces and newly installed workspace deps. |
pr-checks/sync-back.test.ts:43
Sorry, something went wrong.
Since `pr-checks` is now a workspace of the main `package.json`
| Back | FazBrowse Home | New Git URL |
(Based on #3573, which should be merged first.)
Adds an eslint configuration for the pr-checks folder (largely based on the root configuration), updates the .ts files in pr-checks to resolve some linter errors.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Environments:
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist