You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I like this pattern because the same make target is run on your laptop and in CI. Its less work to maintain and you know that whats happens locally is what happen in github ci. When you change your makefiles and you dont have to change your CI workflow files.
The text was updated successfully, but these errors were encountered:
SO i was thinking that CI is really needed, and have been using this approach which you might like to use.
Nice explicit make files:
https://github.com/jerson/openpgp-mobile/blob/flatbuffers/Makefile
Git hub actions just calls the same make files:
https://github.com/jerson/openpgp-mobile/tree/flatbuffers/.github/workflows
That gets you the ability to have the same make target run for many platforms ( desktop, mobile, wasm)
Then because you have many examples to CI, you can wrap the calls to the make file targets with a strategy pattern like here:
https://github.com/amplify-edge/main/blob/master/.github/workflows/ci.yml#L17
Please notice down the very bottom how the make file asked for is then called.
I like this pattern because the same make target is run on your laptop and in CI. Its less work to maintain and you know that whats happens locally is what happen in github ci. When you change your makefiles and you dont have to change your CI workflow files.
The text was updated successfully, but these errors were encountered: