Github Actions

[helio-frota]

We are moving all the repositories to use Github actions.

But we don't have any ideas on getting this "correct way" or at least plans on how to keep these updated and etc...

[helio-frota]

@richardlau any suggestions, hints, comments will be appreciated 👍

[helio-frota]

Since the repo is not private anymore we could probably uncomment these lines https://github.com/nodeshift/new-module-starter/blob/main/.github/workflows/nodejs-ci-action.yml#L27-L48

We have a fooBar test https://github.com/nodeshift/new-module-starter/blob/main/test/test.js#L4
just to make the CI pass and to see the complete flow 👍

@richardlau make sense?

[richardlau]

Sounds good.

[helio-frota]

having this benefit then makes sense for us to start to update all other repositories
#10

[helio-frota]

• new-module-starter chore: use setup-node@v2 #10
• npcheck chore: use coveralls action npcheck#55
• oratrix chore: dependencies updates nodeshift-archived/oratrix#98
• nodejs-cache chore: updating dependencies nodeshift-starters/nodejs-cache#120
• nodejs-rest-http-ts fix: eslint nodeshift-archived/nodejs-rest-http-ts#2
• nodejs-rest-http chore: update dependencies and github action nodeshift-starters/nodejs-rest-http#210
• license-reporter chore: update to use setup-node@v2 github action nodeshift-archived/license-reporter#392
• opossum chore: update to use setu-node@v2 gh action opossum#595
• rhoaster chore: update to use setu-node@v2 gh action nodeshift-archived/rhoaster#85
• opossum-prometheus chore: update to use setu-node@v2 gh action opossum-prometheus#54
• kube-service-bindings chore: update to use setu-node@v2 gh action kube-service-bindings#8
• nodeshift chore: update to use setup-node@v2 gh action nodeshift#583
• openshift-rest-client chore: update to use setu-node@v2 gh action openshift-rest-client#275
• chore: general updates nodeshift-starters/nodejs-health-check#224
• chore: general updates nodeshift-starters/nodejs-configmap#195
• chore: general updates nodeshift-starters/nodejs-rest-http-crud#243

[helio-frota]

for the v2 part the missing repositories are:

https://github.com/nodeshift-starters/nodejs-rest-http-secured
https://github.com/nodeshift-starters/reactive-example

the circuit breaker repos are using travis and rhoaster and that is something we can't migrate now to gh actions

• chore: updates to node.js gh action v2 nodeshift-starters/reactive-example#36
• chore: general updates nodeshift-archived/nodejs-rest-http-secured#183

[helio-frota]

what happens when we finish this? just lock the discussion or delete it?

[richardlau]

I'd rather not delete it. Unfortunately at this time it looks like our options are only delete, lock, or leave open: community/community#3097

[helio-frota]

@richardlau thanks for that info.

let's leave it open then