Skip to content

chore(github): add code scanning and branch route policy - #12

Merged
Iron-Mark merged 1 commit into
mainfrom
dev
Jun 25, 2026
Merged

chore(github): add code scanning and branch route policy#12
Iron-Mark merged 1 commit into
mainfrom
dev

Conversation

@Iron-Mark

Copy link
Copy Markdown
Owner

Summary

  • Adds CodeQL code scanning for JavaScript/TypeScript.
  • Adds a PR Route Policy workflow that allows only dev to target main.
  • Expands CI triggers so dev also receives the same checks before promotion.

Branch model

  • main = production.
  • dev = development/staging integration.
  • Feature branches should open PRs into dev.
  • main should only receive PRs from dev.

Follow-up after merge

After this lands on main, configure GitHub branch protection/rulesets to require CI, CodeQL, and PR Route Policy checks.

## Summary

- Add CodeQL code scanning for main, dev, pull requests, weekly schedule, and manual dispatch.
- Add a PR route policy check so main only accepts PRs from dev, while feature work targets dev.
- Expand CI triggers to cover both main and dev.

## Changes Made
### GitHub Workflows

- Added CodeQL JavaScript/TypeScript analysis.
- Added PR Route Policy workflow.
- Updated CI branch triggers from main-only to main and dev.

## Why

- Keeps main as production, dev as the staging/integration branch, and gives future cloud worktree sessions a safer contribution path.

## Notes for Reviewers

- GitHub branch protection/rulesets should require these checks after the workflow lands on main.
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@Iron-Mark
Iron-Mark merged commit cfb75d9 into main Jun 25, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants