ci: migrate from CircleCI to GitHub Actions

[Juneezee]

Completely migrates from CircleCI to GitHub Actions. Runs lint and test on every push and pull request.

[coveralls]

Pull Request Test Coverage Report for Build 545

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 57.369%

---

Totals
Change from base Build 535:	0.0%
Covered Lines:	3624
Relevant Lines:	6317

---

💛 - Coveralls

[Fontinalis]

I do like the idea of having everything in GitHub Actions and remove CircleCI from the list of tools we use and it's a great PR to replace tests on commits and PRs! 👍🏻

@dhui Thoughts?

[dhui]

Thanks for the PR and helping us improve our release process @Juneezee !

@Fontinalis

I do like the idea of having everything in GitHub Actions and remove CircleCI from the list of tools we use and it's a great PR to replace tests on commits and PRs! 👍🏻

@dhui Thoughts?

Agreed, we should move our tests to use GitHub Actions as well.
Let's keep the other CI and docker files for now in case we need to continue using them. We can clean them up later.

[dhui]

Add workflow_run to the GoReleaser workflow/job (.github/workflows/release.yaml) so that it only runs after tests pass

[Juneezee]

Add workflow_run to the GoReleaser workflow/job (.github/workflows/release.yaml) so that it only runs after tests pass

@dhui There is a caveat if we use workflow_run to trigger the goreleaser job, as described in this StackOverflow answer.

If the goreleaser job is triggered by workflow_run instead of on: push: tags: "v*", GoReleaser would not be able to detect tag that is pushed, which would then cause the job to fail.

EDIT: This leaves us to only 2 choices now (hoping that GitHub could improve the workflow dependencies in the future)

1. Single workflow, dependent jobs: The only possible way at this moment to make goreleaser job run if and only if both lint and test jobs have passed.
2. Separate workflow: This requires the maintainers to be careful and ensure that the tests passed on the latest commit before pushing a tag.

[Fontinalis]

If the goreleaser job is trigerred by workflow_run instead of on: push: tags: "v*", GoReleaser would not be able to detect tag that is pushed, which would then cause the job to fail.

On the other hand, this could be solved if we merge the two workflows into one, and use the following code by @Juneezee to check if the release should run or not

  goreleaser:
    name: Release a new version
    environment: GoReleaser
    runs-on: ubuntu-latest
+   needs: [lint, test]
+   if: ${{ success() && github.repository == 'golang-migrate/migrate' && contains(github.ref, 'refs/tags/v') }}
    ...

So I'm happy to turn my vote on the question of "should we merge the two workflows or not".

[Fontinalis]

Looks legit to me! @dhui you concur?

[Juneezee]

I missed these lines in the previous commit. They are required for coveralls to work correctly with parallel tests, see https://github.com/shogo82148/actions-goveralls#parallel-job-example

[Juneezee]

Last round of review I think, everything seems to be well configured 🚀

[Juneezee]

@dhui Please take a look again 😃

[dhui]

Thanks for migrating our tests over!