[fupacat]

Automated OSS standards remediation for check ci_workflows on fupacat/tsql-scriptdom-java.

[Copilot]

🟡 Changes recommended

The change replaces a working CI workflow with a no-op that validates nothing and targets a non-existent main branch, degrading rather than improving CI/OSS compliance.

2 open findings

• CI workflow no longer builds or tests the project · New
• Push trigger points to non-existent main branch · New

What changed in this PR

This PR, generated by an automated OSS-standards remediation bot, modifies .github/workflows/ci.yml. Despite the title ("add ci.yml to improve OSS standards compliance"), the file already exists, and the change replaces a full build/test workflow with a trivial placeholder. The previous workflow compiled, tested, and packaged the project across a JDK 17/21 matrix, set up Python 3.11 (required by the parser-generation build step), and declared least-privilege permissions. The new build job only runs echo "Running CI checks".

Changes:

• Removes the real CI steps (mvn clean test, mvn package, JDK 17/21 matrix, Python 3.11 setup) and replaces them with a single no-op echo.
• Drops the permissions: contents: read hardening block.
• Changes the push trigger branch from master to a non-existent main, and removes the pull_request branch filter.

File	Description
.github/​workflows/​ci.yml	Overwrites the functional CI workflow with a placeholder that performs no build/test, targets a non-existent main branch, and removes the permissions block.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.