Switch Travis to GitHub Actions

[frbuceta]

See loopbackio/loopback-next#7054

Checklist

• DCO (Developer Certificate of Origin) signed in all commits
• npm test passes on your machine
• New tests added or existing tests modified to cover all changes
• Code conforms with the style guide
• Commit messages are following our guidelines

[frbuceta]

Thats weird! Actions are not executed. Could they be disabled for me? @strongloop/loopback-maintainers

[achrinza]

IIRC, the incoming PR must be from a branch in the main repo (i.e. not a fork); Otherwise, GitHub will not execute the changes until it's merged.

[frbuceta]

IIRC, the incoming PR must be from a branch in the main repo (i.e. not a fork); Otherwise, GitHub will not execute the changes until it's merged.

I don't have permissions to create a branch in this repository, can you give me access?

[mrmodise]

@frbuceta do a pull request to your own folked master it will run pipeline and reference here. @bajtos will need to update the repo settings for it to run Github actions

[frbuceta]

This is the proof that it works correctly https://github.com/frbuceta/loopback-connector-postgresql/pull/1#issue-565051760

[dhmlau]

@frbuceta, thanks for the PR.
I checked the settings. The Actions permission is set to "allow all actions". Not sure where else needs to be changed.
@bajtos, any idea?

[bajtos]

I suspect it's the cause described by @achrinza in his comment #473 (comment) :

IIRC, the incoming PR must be from a branch in the main repo (i.e. not a fork); Otherwise, GitHub will not execute the changes until it's merged.

I think the next step is to merge this PR and then fix any issues in follow-up PRs.

[frbuceta]

I suspect it's the cause described by @achrinza in his comment #473 (comment) :

IIRC, the incoming PR must be from a branch in the main repo (i.e. not a fork); Otherwise, GitHub will not execute the changes until it's merged.

I think the next step is to merge this PR and then fix any issues in follow-up PRs.

As it is now, it should work. You can merge

[bajtos]

The proposal looks great to me!

Let's use a different workflow name please per my comment below.

[bajtos]

Landed, thank you @frbuceta ❤️

[bajtos]

Hmm, the first build failed - see https://github.com/strongloop/loopback-connector-postgresql/actions/runs/530701696

[bajtos]

Reverting this change in #474.

Let's try the new setup in your personal fork first, @frbuceta. Create a feature branch, open a PR against your own repo. Once you fix all issues, then the next step is open a PR from your feature branch to the upstream repo (https://github.com/strongloop/loopback-connector-postgresql).

[agnes512]

this might help https://github.com/marketplace/actions/setup-postgresql

[frbuceta]

this might help https://github.com/marketplace/actions/setup-postgresql

This is a shortcut to what we are using right now in the code. This afternoon we have executed (@bajtos) the code in my fork but here it is not working correctly. @bajtos is investigating why this happens.

See https://github.com/frbuceta/loopback-connector-postgresql/pull/1

[bajtos]

Sorry for the delay. There is a lot on my plate these days and what's worse, I fell sick. It makes me wonder, would you @agnes512 have bandwith to take over this work from me? My idea was to create a new feature branch in this repo, cherry-pick @frbuceta's commit, open a pull request and then tweak the settings or our tests until all GH actions are passing.