Readme: Add Github Actions nightly workflow status badge

[Ayesh]

Follows-up #8970.

[TimWolla]

I'm not sure if "Nightly" is the correct choice to display, as that one is highly dynamic. I think the "Push" workflow would be more appropriate, as that's specific to master and thus consistent with the other services to my understanding.

[iluuu1994]

I agree with Tim, this should probably use the push workflow. The nightly workflow tests all changed branches. It would be nice to display nightly test results per branch, but that would require splitting up the workflow.

[Ayesh]

Thank you @iluuu1994 and @TimWolla, changed now.

It would be nice to display nightly test results per branch, but that would require splitting up the workflow.

I can imagine a matrix like this being quite helpful:

OS/Architecture	PHP 7.4	PHP 8.0	PHP 8.1	master
Linux x64	--	--	--	--
Windows x64	--	--	--	--
Mac OS	--	--	--	--

Unfortunately it doesn't look like we can do it yet, unless we use a service like shields.io to fetch the status of each item in a job matrix and generate SVG. Too complicated to pull, I'd say.

[mvorisek]

Nightly badge should go probably after the build statuses and before fuzzer.

The standard (non nightly) build statuses should have an individual badge per php version/branch, which should be supported - https://github.community/t/workflow-status-badge-per-branch/16198/5

[Ayesh]

The order now is Travis, Appveyor, Azure, Github Actions.

The standard (non nightly) build statuses should have an individual badge per php version/branch, which should be supported - https://github.community/t/workflow-status-badge-per-branch/16198/5

PHP-7.4 branch does not use the current line of CIs. I tried the nightly builds with the branch parameter changed, but the badges don't seem to be working correctly.

[iluuu1994]

The order now is Travis, Appveyor, Azure, Github Actions.

I'd show the GitHub Actions badge first, as it's likely includes the most important jobs (x86-64 for Linux).

I tried the nightly builds with the branch parameter changed, but the badges don't seem to be working correctly.

I don't think that's how it works. The branch parameter will check which branch the workflow was triggered on. However, nightly is always triggered from master as all cron workflows are only triggered on the default branch.

[Ayesh]

Thank you. I just figured that the nightly.yml in master branch cleverly runs the builds on all active branches. But for status badges, you are right we can't really do it given the lack of the feature we have.

I also changed the order so GH Actions is shown first:

[mvorisek]

Suggested change

	[](https://travis-ci.com/github/php/php-src)
	[](https://ci.appveyor.com/project/php/php-src)
	[](https://dev.azure.com/phpazuredevops/php/_build/latest?definitionId=1&branchName=master)
	[](https://github.com/php/php-src/actions/workflows/push.yml)
	[](https://github.com/php/php-src/actions/workflows/push.yml?query=branch%3APHP-8.0)
	[](https://github.com/php/php-src/actions/workflows/push.yml?query=branch%3APHP-8.1)
	[](https://github.com/php/php-src/actions/workflows/push.yml?query=branch%3Amaster)
	[](https://travis-ci.com/github/php/php-src)
	[](https://ci.appveyor.com/project/php/php-src)
	[](https://dev.azure.com/phpazuredevops/php/_build/latest?definitionId=1&branchName=master)

here is how it is rendered: https://github.com/php/php-src/blob/ff9cf9e4bcb855b67dc21bf27ead57199ba81f51/README.md, the badge annotation is not displayed... maybe we should introduce 3 separate lines for each supported PHP version

GH should be first, it will shortly test Windows as well

and for each line/version, nightly should be 2nd badge and the workflow should be changed, so it is triggered from cron on master on every branch - https://github.com/php/php-src/actions/workflows/nightly.yml?query=branch%3APHP-8.1

[iluuu1994]

Thank you @Ayesh! Any further improvements like a matrix can be done in a follow up.