Skip to content

atlasaction: support git-base and git-dir for migrate/lint action #2093

atlasaction: support git-base and git-dir for migrate/lint action

atlasaction: support git-base and git-dir for migrate/lint action #2093

Triggered via pull request July 23, 2025 10:59
Status Success
Total duration 1m 54s
Artifacts

ci-go.yaml

on: pull_request
Matrix: schema-apply
Matrix: schema-lint
Fit to window
Zoom out
Zoom in

Annotations

38 errors, 34 warnings, and 2 notices
schema-apply (multiple-envs, file://20240910173744.plan.hcl, iHZMQ1EoarAXt/KU0KQbBljbbGs8gVqX2ZBX...
Abort: The plan "From" hash does not match the current state hash (passed with --from): - iHZMQ1EoarAXt/KU0KQbBljbbGs8gVqX2ZBXefePSGE= (plan value) + R1cGcSfo1oWYK4dz+7WvgCtE/QppFo9lKFEqEDzoS4o= (current hash)
schema-apply (approval/lint-review, ERROR, cannot apply a migration plan in a PENDING state)
Error: cannot apply a migration plan in a PENDING state. Approve the plan first to proceed: atlas schema plan approve --url atlas://atlas-action/plans/pr-427-8731366c
schema-apply (legacy, true, v0.29.0, multiple pre-planned migrations were found)
Error: multiple pre-planned migrations were found in the registry for this schema transition. Current hash: R1cGcSfo1oWYK4dz+7WvgCtE/QppFo9lKFEqEDzoS4o= Desired hash: ufnTS7NrAgkvQlxbpnSxj119MAPGNqVj0i3Eelv+iLc= Plans found: atlas://atlas-action/plans/pr-252-R1cGcSfo atlas://atlas-action/plans/pr-253-R1cGcSfo atlas://atlas-action/plans/pr-254-R1cGcSfo atlas://atlas-action/plans/pr-255-R1cGcSfo atlas://atlas-action/plans/pr-256-R1cGcSfo To resolve the issue, either delete the conflicting plans or provide the plan URL explicitly using the --plan flag.
schema-apply (lint-review, errors or warnings were found)
The process exited with code 1
schema-apply (lint-review, errors or warnings were found)
Rejected by review policy: errors or warnings were found
schema-test
The process exited with code 1
schema-test
`atlas schema test` completed with errors: -- FAIL: expected_failure (104µs) schema.test.hcl:9: Error: output not equal: expected `0`, but got "" FAIL
schema-lint (sqlite://schemarule.db)
The process exited with code 1
schema-lint (sqlite://schemarule.db)
`atlas schema lint` completed successfully with 1 errors and 2 warnings, check the annotations for details
primary-key-required rule violated
Table T1 must have a primary key
schema-apply (approval/pending, ALWAYS, cannot apply a migration plan in a PENDING state)
Error: cannot apply a migration plan in a PENDING state. Approve the plan first to proceed: atlas schema plan approve --url atlas://atlas-action/plans/pr-427-1d23cca1
migrate-down
The process exited with code 1
migrate-down
plan rejected, review here: ABORTED_URL
migrate-down
The process exited with code 1
migrate-down
plan approval pending, review here: PENDING_URL
migrate-down
The process exited with code 1
migrate-down
plan approval pending, review here: PENDING_URL
migrate-test
The process exited with code 1
migrate-test
`atlas migrate test` completed with errors: -- FAIL: expected_failure (625µs) migrations.test.hcl:15: Error: output not equal: expected `0`, but got "" FAIL
migrate-test
The process exited with code 1
migrate-test
`atlas migrate lint` completed with errors, see report: https://ariga-atlas.atlasgo.cloud/ci-runs/8589947715
destructive changes detected: atlasaction/testdata/migrations_destructive/20230925192914.sql#L1
Dropping table "t1" (DS102) Details: https://atlasgo.io/lint/analyzers#DS102
schema-lint (file://schema.lt.hcl)
The process exited with code 1
schema-lint (file://schema.lt.hcl)
`atlas schema lint` completed successfully with 1 errors and 2 warnings, check the annotations for details
schema-apply (approval/lint-review, ERROR, was not approved within the specified waiting period, 5s)
the schema plan "pr-427-843cbeef" was not approved within the specified waiting period. Please review the plan and re-run the action. You can approve the plan by visiting: https://ariga-atlas.atlasgo.cloud/schemas/141733920798/plans/210453401193
schema-apply (approval/pending, ALWAYS, was not approved within the specified waiting period, 5s)
the schema plan "pr-427-9b4f5608" was not approved within the specified waiting period. Please review the plan and re-run the action. You can approve the plan by visiting: https://ariga-atlas.atlasgo.cloud/schemas/141733920798/plans/210453401192
unit-tests
`atlas migrate test` completed with errors: Failure
unit-tests
`atlas schema test` completed with errors: Failure
unit-tests
Abort: The plan "From" hash does not match the current state hash (passed with --from): - iHZMQ1EoarAXt/KU0KQbBljbbGs8gVqX2ZBXefePSGE= (plan value) + R1cGcSfo1oWYK4dz+7WvgCtE/QppFo9lKFEqEDzoS4o= (current hash)
unit-tests
Rejected by review policy: errors or warnings were found
schema-apply (multiple-envs, file://20240910173744.plan.hcl, iHZMQ1EoarAXt/KU0KQbBljbbGs8gVqX2ZBX...
Abort: The plan "From" hash does not match the current state hash (passed with --from): - iHZMQ1EoarAXt/KU0KQbBljbbGs8gVqX2ZBXefePSGE= (plan value) + R1cGcSfo1oWYK4dz+7WvgCtE/QppFo9lKFEqEDzoS4o= (current hash)
schema-apply (multiple-envs, file://20240910173744.plan.hcl, iHZMQ1EoarAXt/KU0KQbBljbbGs8gVqX2ZBX...
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
schema-apply (approval/lint-review, ERROR, cannot apply a migration plan in a PENDING state)
Error: cannot apply a migration plan in a PENDING state. Approve the plan first to proceed: atlas schema plan approve --url atlas://atlas-action/plans/pr-427-8731366c
schema-apply (approval/lint-review, ERROR, cannot apply a migration plan in a PENDING state)
Schema plan is pending approval, review here: https://ariga-atlas.atlasgo.cloud/schemas/141733920798/plans/210453401191
schema-apply (approval/lint-review, ERROR, cannot apply a migration plan in a PENDING state)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
schema-apply (legacy, true, v0.29.0, multiple pre-planned migrations were found)
Error: multiple pre-planned migrations were found in the registry for this schema transition. Current hash: R1cGcSfo1oWYK4dz+7WvgCtE/QppFo9lKFEqEDzoS4o= Desired hash: ufnTS7NrAgkvQlxbpnSxj119MAPGNqVj0i3Eelv+iLc= Plans found: atlas://atlas-action/plans/pr-252-R1cGcSfo atlas://atlas-action/plans/pr-253-R1cGcSfo atlas://atlas-action/plans/pr-254-R1cGcSfo atlas://atlas-action/plans/pr-255-R1cGcSfo atlas://atlas-action/plans/pr-256-R1cGcSfo To resolve the issue, either delete the conflicting plans or provide the plan URL explicitly using the --plan flag.
schema-apply (legacy, true, v0.29.0, multiple pre-planned migrations were found)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
schema-apply (lint-review, errors or warnings were found)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
primary-key-required rule violated
Table T1 must have a primary key
naming violations detected
Table "main.T1" violates the naming policy (NM102) Details: https://atlasgo.io/lint/analyzers#NM102
schema-apply (local-plan, file://20240910173744.plan.hcl)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
schema-apply (approval/no-changes, ALWAYS)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
schema-apply (approval/pending, ALWAYS, cannot apply a migration plan in a PENDING state)
Error: cannot apply a migration plan in a PENDING state. Approve the plan first to proceed: atlas schema plan approve --url atlas://atlas-action/plans/pr-427-1d23cca1
schema-apply (approval/pending, ALWAYS, cannot apply a migration plan in a PENDING state)
Schema plan is pending approval, review here: https://ariga-atlas.atlasgo.cloud/schemas/141733920798/plans/210453401194
schema-apply (approval/pending, ALWAYS, cannot apply a migration plan in a PENDING state)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
migrate-down
plan has not been approved in configured waiting period, exiting
schema-apply (on-the-fly, true)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
schema-apply (approval/approved, ALWAYS)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
schema-apply (remote-repo, atlas://atlas-action/plans/20240910183610, atlas://atlas-action?tag=e2e)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
migrate-test
What's next: Try Atlas Copilot to suggest custom linting rules for your schema → atlas copilot 'Suggest custom linting rules for my schema' Learn more: https://atlasgo.io/lint/rules
schema-lint (file://schema.lt.hcl): atlasaction/testdata/schema-lint/schema.lt.hcl#L1
Table "t2" violates the naming policy (NM102) Details: https://atlasgo.io/lint/analyzers#NM102
schema-lint (file://schema.lt.hcl): atlasaction/testdata/schema-lint/schema.lt.hcl#L1
Table "t1" violates the naming policy (NM102) Details: https://atlasgo.io/lint/analyzers#NM102
schema-apply (approval/lint-review, ERROR, was not approved within the specified waiting period, 5s)
Schema plan is pending approval, review here: https://ariga-atlas.atlasgo.cloud/schemas/141733920798/plans/210453401193
schema-apply (approval/lint-review, ERROR, was not approved within the specified waiting period, 5s)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
schema-apply (approval/pending, ALWAYS, was not approved within the specified waiting period, 5s)
Schema plan is pending approval, review here: https://ariga-atlas.atlasgo.cloud/schemas/141733920798/plans/210453401192
schema-apply (approval/pending, ALWAYS, was not approved within the specified waiting period, 5s)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
golangci-lint
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>08cCAaAAAAAANlnq4ofd0TIQIMF/Y8OaLQkwyQUEyMDMwMTA5MDUzAEVkZ2U=
golangci-lint
Failed to restore: Cache service responded with 400
unit-tests
Failure
unit-tests
Failure
unit-tests
Abort: The plan "From" hash does not match the current state hash (passed with --from): - iHZMQ1EoarAXt/KU0KQbBljbbGs8gVqX2ZBXefePSGE= (plan value) + R1cGcSfo1oWYK4dz+7WvgCtE/QppFo9lKFEqEDzoS4o= (current hash)
unit-tests
Error: quota error
Expected Failure
sqlite://schemarule.db failed as expected
Expected Failure
file://schema.lt.hcl failed as expected