To maintain the integrity of the LLAMOSC framework and ensure that GSoC contributions meet our research standards, we need to implement stricter repository safeguards. Recent PRs have introduced syntax errors and simplified core logic that bypasses our sustainability goals. This issue aims to stabilize the project by enforcing a professional development workflow.
The Goal
Implement GitHub RuleSets, automated CI protections, and AI-assisted reviews to ensure no code is merged into main without passing rigorous quality and research-alignment checks.
Requirements
- Enforce PR-Only Workflow via develop Branch:
- Update the LLAMOSC README to state that all new PRs must be opened against the develop branch first, not main.
- Enable GitHub Branch Protection on main to ensure all contributors must use the PR process; direct pushes to main must be disabled to prevent unauthorized logic changes.
- CI Validation: Integrate a GitHub Action that runs automated tests and linters on every PR to catch SyntaxError, ImportError, or regressions before they reach the codebase.
- AI-Assisted Code Reviews (GitHub Copilot): Configure/Enable GitHub Copilot for PR summaries and reviews. The review process must:
- Flag any detrimental logic changes to core research agents.
- Verify that a PR does not close an issue if the requirements are not fully resolved (preventing "quick fixes" from closing complex issues).
- Code Integrity (Code Owners): Create a CODEOWNERS file to require mandatory maintainer approval for any changes to critical files located under:
- Open Source Sustainibility using LLMs/ (including all agent logic, simulations, and prompts).
- Documentation: Add a CONTRIBUTING.md section explaining that contributors must not alter tried-and-tested prompt logic without providing a research-backed justification.
Why this is a "Good First Issue"
This is a high-impact task for someone familiar with GitHub Actions, Repo Infrastructure, and AI-assisted workflows. It is essential for stabilizing the project's foundation before the GSoC application period begins.
To maintain the integrity of the LLAMOSC framework and ensure that GSoC contributions meet our research standards, we need to implement stricter repository safeguards. Recent PRs have introduced syntax errors and simplified core logic that bypasses our sustainability goals. This issue aims to stabilize the project by enforcing a professional development workflow.
The Goal
Implement GitHub RuleSets, automated CI protections, and AI-assisted reviews to ensure no code is merged into main without passing rigorous quality and research-alignment checks.
Requirements
Why this is a "Good First Issue"
This is a high-impact task for someone familiar with GitHub Actions, Repo Infrastructure, and AI-assisted workflows. It is essential for stabilizing the project's foundation before the GSoC application period begins.