Recently, I've been working a lot more with GitHub Actions - both writing actions and creating CI pipelines for projects.
Last week I picked up a ...
For further actions, you may consider blocking this person and/or reporting abuse
Great write up!
Switching between branches can be avoided since we can simply fetch and then use "origin/master":
Thank Tierney for a great post. Very much appreciated!
Do you have a working example with this solution?
I couldn't bring it to work. With you example:
This can't be resolved in my actions. I used this instead:
But jest still behaves very weirdly. It still doesn't recognize any changes, even though there are certainly changes with master.
Here's an example of where it worked - we've since moved past it to a different model, but this CI setup fully worked: github.com/nodejs/examples/pull/4
I am trying to implement this change in the pull request event as result jest wants to execute all test
Would this be advisable for PR's that perform automatic dependency updates like Dependabot or Renovate or would I need to add a separate workflow for that?
With actions/checkout@v3 now theres a cleaner way to do it: