chore: remove redundant main.yaml CI workflow#94
Conversation
| name: Test Baton Gitlab Integration | ||
|
|
||
| on: pull_request | ||
| on: |
There was a problem hiding this comment.
i think you can also remove the go-test and go-lint jobs in this file those should be covered in the verfiy.yaml from baton-admin
Connector PR Review: chore: remove redundant main.yaml CI workflowBlocking Issues: 1 | Suggestions: 1 | Threads Resolved: 0 Review SummaryReviewed the full PR diff (workflow-only changes; no Go source, Security IssuesNone found. Correctness Issues
Suggestions
Prompt for AI agents |
| branches: | ||
| - main | ||
|
|
||
| jobs: |
There was a problem hiding this comment.
🟠 Bug: This PR removes the go-lint and go-test jobs from ci.yaml and also deletes main.yaml, which was the only other place those jobs ran. After this change no workflow in the repo runs golangci-lint or go test on pull requests or on push to main — capabilities_and_config.yaml only does go build, and update-dependencies.yaml is a scheduled maintenance job. The PR description says these jobs are "already covered by ci.yaml," but this same diff removes them. Unless a centralized reusable workflow (not present in this repo) runs lint/test, please keep a go-lint/go-test job on pull_request. (confidence: medium-high)
There was a problem hiding this comment.
Not a bug — lint/test are covered by the managed verify workflow (baton-admin), which is why @gontzess asked to drop these here. It is not a file in this repo, but verify / lint and verify / test run and pass on this PR, and also run on push to main (confirmed on the latest main commit). So no lint/test coverage is lost by removing the local go-lint/go-test jobs.
| push: | ||
| branches: | ||
| - main |
There was a problem hiding this comment.
🟡 Suggestion: This adds a push: branches: [main] trigger, but the only remaining job (test-cloud-version) is now guarded by if: github.event_name == 'pull_request', so it is skipped on push. The push-to-main trigger therefore runs zero jobs and is effectively a no-op. If the intent was to run lint/test on push to main (as main.yaml previously did), that coverage is now missing. (confidence: high)
There was a problem hiding this comment.
Good catch — fixed in 9905983. Since verify already covers lint/test on push to main, the push: [main] trigger here only pointed at the PR-only test-cloud-version job (zero jobs on push). Switched to on: pull_request and dropped the now-redundant if: github.event_name == 'pull_request' guard.
| @@ -3,45 +3,6 @@ name: Test Baton Gitlab Integration | |||
| on: pull_request | |||
|
|
|||
| jobs: | |||
There was a problem hiding this comment.
🟠 Bug: This PR removes the go-lint and go-test jobs from ci.yaml in addition to deleting main.yaml. After merge, no workflow runs golangci-lint or go test on pull_request or push to main (the other workflows only go build or run integration tests needing secrets). The PR describes main.yaml as a redundant duplicate of jobs "already covered by ci.yaml," but this diff also deletes those jobs from ci.yaml, so lint/unit-test coverage is eliminated rather than deduplicated. If deduplication was the intent, keep go-lint/go-test in ci.yaml and only delete main.yaml.
Connector PR Review: chore: remove redundant main.yaml CI workflowBlocking Issues: 0 | Suggestions: 1 | Threads Resolved: 0 Review SummaryThe full PR diff was scanned for security and correctness. Beyond the CI workflow cleanup, this PR also migrates deprecated SDK trait options (WithGroupProfile/WithUserProfile/WithStatus) to the resource-level WithResourceProfile/WithResourceStatus in groups.go, projects.go, and users.go; that migration is correct — the trait is still created via the (now empty) trait-option slices, and the new ResourceOption signatures match the vendored SDK. The go-test job remains and runs on both pull_request and push to main, so the earlier concern about lost test coverage and a no-op push trigger does not apply. One suggestion remains regarding lint coverage. Security IssuesNone found. Correctness IssuesNone found. Suggestions
Prompt for AI agents |
main.yaml duplicated the go-lint/go-test jobs already covered by ci.yaml, just triggered on push to main instead of pull_request. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
main.yaml previously ran go-lint/go-test on push to main; now that it's removed, ci.yaml picks up that trigger directly. test-cloud-version stays PR-only since it hits the real GitLab API and wasn't part of main.yaml's scope. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
9905983 to
1a59dc5
Compare
Migrate WithGroupProfile/WithUserProfile/WithStatus (deprecated, SA1019) to the resource-level WithResourceProfile/WithResourceStatus options in groups.go, projects.go, and users.go. Remove the redundant go-lint job from the "Test Baton Gitlab Integration" workflow; verify.yaml's `verify / lint` already covers it. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
| version: latest | ||
| args: --timeout=3m | ||
|
|
||
| go-test: |
There was a problem hiding this comment.
🟡 Suggestion: This PR removes the go-lint job from ci.yaml and deletes main.yaml (which also ran golangci-lint), leaving no workflow that runs golangci-lint on PRs or pushes to main. The commit intent was to deduplicate the lint job, but it's now eliminated entirely rather than kept in one place. Unless the shared verify.yaml@v4 reusable workflow runs lint, consider keeping a single go-lint job here. (medium confidence — depends on what the shared verify workflow covers)
Summary
.github/workflows/main.yaml, which duplicated thego-lint/go-testjobs already covered byci.yaml, just triggered on push tomaininstead ofpull_request.Test plan
🤖 Generated with Claude Code