Skip to content

ci: add PR check suite (CI + CodeQL + Dependabot)#11

Merged
moose-lab merged 6 commits into
mainfrom
ci/initial-setup
May 26, 2026
Merged

ci: add PR check suite (CI + CodeQL + Dependabot)#11
moose-lab merged 6 commits into
mainfrom
ci/initial-setup

Conversation

@moose-lab

Copy link
Copy Markdown
Owner

What

Introduces the initial CI/CD check suite for pull requests.

Workflows

File Trigger Required for merge?
`.github/workflows/ci.yml` PR + push to main yes (job: `CI`)
`.github/workflows/codeql.yml` PR + push to main + weekly cron yes (job: `CodeQL`)
`.github/dependabot.yml` weekly schedule n/a (config only)

CI job

Checkout → setup Bun `1.3.14` → setup Node `20` → `bun install --frozen-lockfile` → `typecheck` → `test` → `next build` → `tsup` (CLI build). Sequential single job to amortize the `bun install` cost (native deps: `better-sqlite3`, `node-pty`). Concurrency group cancels superseded runs on the same ref.

CodeQL

`javascript-typescript` with `security-and-quality` query suite, Monday 06:00 UTC cron.

Dependabot

Weekly npm + github-actions updates, minor/patch grouped per ecosystem, max 5 open PRs each, assigned to @moose-lab.

Follow-up after merge

Branch protection on `main` will be applied separately so the required-check contexts (`CI`, `CodeQL`) have been observed at least once on the default branch first.

Protection settings to be applied:

  • required status checks (strict): `CI`, `CodeQL`
  • required PR (0 approvals)
  • required linear history
  • required conversation resolution
  • no force-push, no deletion
  • `enforce_admins: false` (admin escape hatch preserved)
  • signed commits not required

@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.

@moose-lab
moose-lab merged commit e9d42f1 into main May 26, 2026
3 checks passed
@moose-lab
moose-lab deleted the ci/initial-setup branch May 26, 2026 15:05
loop2zero added a commit to loop2zero/DevLog that referenced this pull request Jun 11, 2026
#1)

Chained subtasks merge remotely while the local default branch never
advances, so each new worktree was cut from a stale base and every PR in
the chain conflicted (ARC-104 PR moose-lab#10, ARC-105 PR moose-lab#11).

createWorktree now fetches origin/<baseBranch> and bases the new branch
on the remote tip via resolveWorktreeBase; when the fetch fails (offline
or no remote) it logs a warning and degrades to the local branch so
dispatch is never blocked. createWorktreeAt is the repo-root-level core,
extracted so tests can run against a temp repo with a local bare remote.

ARC-108

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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