🔄 synced file(s) with OrrisTech/.github

[iamzifei]

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

• synced local .github/workflows/ci.yml with remote sync/.github/workflows/ci.yml

---

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

[github-actions]

React Doctor Report

Click to expand results

npm warn exec The following package was not found and will be installed: react-doctor@0.0.28
react-doctor v0.0.28

�[2mScanning /home/runner/work/clawface/clawface...�[22m


�[31mSomething went wrong. Please check the error below for more details.�[39m
�[31mIf the problem persists, please open an issue on GitHub.�[39m
�[31m�[39m
�[31mNo React dependency found in package.json�[39m

Powered by react-doctor

[Copilot]

Pull request overview

Syncs this repo’s CI caller workflow with the organization-standard workflow from OrrisTech/.github, updating how lint/typecheck and security jobs are treated in CI.

Changes:

• Removed continue-on-error: true from lint-typecheck and security jobs.
• Updated inline comments describing those jobs’ blocking/advisory behavior.

---

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

[Copilot]

Same issue here: removing continue-on-error: true means a security audit failure will fail the overall workflow run. The “advisory only / won’t block” comments should either be corrected, or continue-on-error: true should be restored if this job is intended to be non-blocking.

Suggested change

	# No "needs:" from other jobs, so failures here won't block CI.
	# No "needs:" from other jobs, so failures here won't block CI.
	continue-on-error: true

[Copilot]

These comments are inaccurate: even without needs, a failing job still makes the workflow run fail (and will block merges if this workflow is a required check). If the intent is truly “advisory only”, re-add continue-on-error: true; otherwise update/remove the “Advisory only / won’t block CI” wording to reflect that failures will fail the CI check.