tests: migrate from Travis to GitHub-Actions

[kiranparajuli589]

Description

• migrate from travis to gh-actions

Motivation

• tests: migrate from Travis to GitHub Actions xml#206

Related

• fork pr: https://github.com/kiranparajuli589/vobject/pull/1 (you can see the build status here)

[phil-davis]

@DeepDiver1975 I thought that I had access to repo settings, but it seems not. Maybe you can remove Travis as an expected CI result, and enable GitHub Actions etc?

[staabm]

I just removed prettyCI and travisCI from the whole sabre-io.org

[staabm]

after we merged the PR and the first github action was run, we can declare it as a required check

[phil-davis]

@staabm is there a way to get the GitHub actions to run on this PR? Or do we review and "just merge it" and then see if it works?

[staabm]

GitHub actions to run on this PR? Or do we review and "just merge it" and then see if it works?

AFAIK the github actions would run within the PR immediately when the PR is created by a person with write-access to the repo.

for other people it runs only after merge

[phil-davis]

for other people it runs only after merge

Yesterday I saw a button to click on PR sabre-io/xml#204 to give it permission to run the GitHub Actions CI. (That PR was from a fork) I clicked it, CI ran, passed, then we merged,

But I don't see that option here. But maybe that is because this is the very first PR that is actually implementing the GitHub actions.

[phil-davis]

LGTM - we can see what happens when this is merged - I will make a PR and test and we can easily do any minor changes that are needed.

[phil-davis]

IMO composer phpunit does not run with coverage, so we might not get any coverage data.