ci(workflows): add run-test and run-lint toggles to go-ci

[scttbnsn]

Summary

• go-ci.yml's test and lint jobs ran unconditionally, so a Go-less repo (e.g. drydock, pure TypeScript) that only wants the language-agnostic workflow-security (zizmor) job could not call this reusable workflow at all.
• Add run-test and run-lint boolean inputs, defaulting to true, and gate the test and lint jobs with the same if: inputs.run-<x> idiom already used for run-govulncheck, run-workflow-security, run-codeql, run-qlty, run-goreleaser, and run-commit-message. This mirrors node-ci.yml's existing run-lint/run-test/run-build pattern (which defaults to false there, since Node CI has no fixed always-on job).
• Defaults preserve behavior for every existing caller (portwing, sockguard, drydock) pinned at the current frozen SHA — nothing changes until a consumer adopts a new frozen SHA rolled deliberately.
• No job in go-ci.yml uses needs: against test or lint and none reads their outputs, so toggling either off cannot cascade-skip or fail a downstream job — no always()/result-handling changes were needed.
• Extended .github/tests/reusable_ci_contract_test.py to assert the two new inputs exist with type: boolean and default: true, keeping the reusable-workflow contract test authoritative.

Scoped to option 1 from #18 only. The node-ci.yml module-directory gap noted in the issue is a separate follow-up, untouched here.

Fixes: #18

Test plan

• python3 .github/tests/reusable_ci_contract_test.py — all 11 tests pass
• python3 .github/tests/community_health_contract_test.py, greptile_summon_contract_test.py, greptile_config_contract_test.py, quality_report_contract_test.py — pass (unaffected, run for regression safety)
• actionlint .github/workflows/go-ci.yml — clean
• zizmor --no-online-audits .github/workflows/go-ci.yml — no findings
• Ruby YAML.parse_file on the workflow — parses

Summary by CodeRabbit

• New Features

  • Added optional controls to enable or skip automated testing and linting in the Go CI workflow.
  • Both checks remain enabled by default.

• Tests

  • Updated workflow validation to verify the new testing and linting controls.

[scttbnsn]

@coderabbitai review

[coderabbitai]

⚠️ Action not completed

Already reviewed.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Important

Review skipped

No new commits to review since the last review.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: f6fda2ed-5ac2-4648-95b1-cd1a3dc353f3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 84603abb-21ad-4181-abc1-cf0b3f1907d9

📥 Commits

Reviewing files that changed from the base of the PR and between e30a84d and 488b89e.

📒 Files selected for processing (2)

• .github/tests/reusable_ci_contract_test.py
• .github/workflows/go-ci.yml

Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The reusable Go CI workflow now accepts run-test and run-lint boolean inputs. Both default to true. The test and lint jobs use these inputs as execution conditions. Contract tests validate the input definitions.

Changes

Go CI job controls

Layer / File(s)	Summary
Workflow input contract .github/workflows/go-ci.yml, .github/tests/reusable_ci_contract_test.py	The workflow defines run-test and run-lint as boolean inputs with true defaults. Contract tests validate their names, types, and defaults.
Conditional test and lint jobs .github/workflows/go-ci.yml	The test job runs only when inputs.run-test is true. The lint job runs only when inputs.run-lint is true.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 488b8

The reusable Go CI workflow adds boolean toggles for its test and lint jobs while keeping both enabled by default, so existing consumers retain their behavior and Go-less repositories can disable those jobs when needed. No actionable merge-blocking risk remains after normal checks and review.

Possibly related PRs

• CodesWhat/.github#13: Introduced the reusable Go CI workflow and its contract tests extended by this change.

Suggested reviewers: biggest-littlest, alargecompany

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	The changes satisfy issue #18 by adding boolean run-test and run-lint inputs that default to true and gate the corresponding jobs.
Out of Scope Changes check	✅ Passed	All changes support issue #18 and no unrelated code or workflow changes are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the addition of run-test and run-lint toggles to the Go CI workflow.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/go-ci-run-test-lint-toggles

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[biggest-littlest]

Toggle pattern matches the existing run-* idiom, defaults preserve behavior for pinned callers, contract test updated.

[ALARGECOMPANY]

Verified no needs: edges on test/lint, so the if: gates can't cascade. Good to land.