Thanks. This is really good. Ive been super frustarted by Github Actions for a while now. My own fault for not investing enough time in learning them, but this is a super useful resource
Nice content! I use GitHub Actions on my job's org to integrate the repositories with SonarCloud and check PRs for semantic commits. Can you make a video about good practices for updating a Go module to a major version like v2, v3, and so on?
Thanks for the great video! Would it make sense to combine the linter and test workflow into a single one so that we don't have to check out the code twice and share the same runner?
You certainly could do that. The reason I usually keep them separate, though, is because I want to run both for every PR, even of one fails. And it's easier to see the failures if they are in separate jobs. But if that doesn't apply to you, by all means, you can combine them.
Thanks. This is really good. Ive been super frustarted by Github Actions for a while now. My own fault for not investing enough time in learning them, but this is a super useful resource
Thanks for sharing!!!
Nice content! I use GitHub Actions on my job's org to integrate the repositories with SonarCloud and check PRs for semantic commits.
Can you make a video about good practices for updating a Go module to a major version like v2, v3, and so on?
Nice suggestion. I'll add it to my list.
Thanks for the great video! Would it make sense to combine the linter and test workflow into a single one so that we don't have to check out the code twice and share the same runner?
You certainly could do that.
The reason I usually keep them separate, though, is because I want to run both for every PR, even of one fails. And it's easier to see the failures if they are in separate jobs.
But if that doesn't apply to you, by all means, you can combine them.
Why did you manually add the license instead of selecting it while creating the repo? Thanks for the great video on starting a project.
Because I wanted to demonstrate the entire process.