Skip to content
This repository has been archived by the owner on Dec 11, 2020. It is now read-only.

Enhancement: Switch to using GitHub actions #1847

Merged
merged 6 commits into from
Dec 2, 2019

Conversation

localheinz
Copy link
Contributor

This PR

  • switches to using GitHub actions

@localheinz localheinz self-assigned this Nov 14, 2019
@localheinz localheinz added this to the 2.0.0 milestone Nov 14, 2019
@localheinz localheinz force-pushed the feature/github-actions branch from b2ca95d to 1e9ecf2 Compare November 14, 2019 14:56
php:
- 7.2
- 7.3
- nightly
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't run on nightly - do we care?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No really if you ask me. Isnt there a 7.4 image available already since release is in 2 weeks from now.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is available now, yes!

- name: "Install PHP with extensions"
uses: shivammathur/[email protected]
with:
php-version: 7.1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we running phpcs only for 7.1 at this point? No idea if we could actually have a diff there based on a PHPversion. Dont really think so though

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pimjansen

I think it suffices to run a coding standards fixer on the lowest supported version of PHP.

@@ -0,0 +1,76 @@
# https://help.github.com/en/categories/automating-your-workflow-with-github-actions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let me just add a comment on rootlevel. Isnt it maybe wise to integrate all tooling already that we want to have implemented? Like PHPstan and maybe some comp. checks or will we add them later

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pimjansen

I'd prefer to add them later, one by one.

@localheinz localheinz force-pushed the feature/github-actions branch 2 times, most recently from 52c0b13 to 93ff7c3 Compare November 23, 2019 11:11
@localheinz
Copy link
Contributor Author

@fzaninotto

Looks like Actions aren't enabled - at least they are not running and there are no complaints about invalid YML configuration either.

Can you double-check that GitHub Actions are enable?

Screen Shot 2019-11-23 at 12 12 33

Could also be that they are not activated because I do not have push privileges.

@localheinz localheinz force-pushed the feature/github-actions branch from 93ff7c3 to 8b80f88 Compare November 23, 2019 11:14
@localheinz localheinz marked this pull request as ready for review November 23, 2019 11:14
@localheinz localheinz force-pushed the feature/github-actions branch from 8b80f88 to 3d749eb Compare November 23, 2019 11:14
@localheinz localheinz mentioned this pull request Nov 26, 2019
1 task
@fzaninotto
Copy link
Owner

Yes, actions are enabled... Dunno what's wrong.

@pimjansen
Copy link
Contributor

I see that there is now something within actions, so maybe if we rebase this it should be fine i guess

@localheinz
Copy link
Contributor Author

@pimjansen

Will do!

@localheinz localheinz force-pushed the feature/github-actions branch 2 times, most recently from 1a8f5c3 to 7d0316a Compare November 28, 2019 09:29
@localheinz
Copy link
Contributor Author

@fzaninotto @pimjansen

Looking good!

@localheinz localheinz force-pushed the feature/github-actions branch 3 times, most recently from ca3a0d6 to e0c009a Compare November 28, 2019 09:47
@localheinz localheinz removed their assignment Nov 28, 2019
@localheinz
Copy link
Contributor Author

I need to collect code coverage here as well, give me a moment!

@localheinz localheinz force-pushed the feature/github-actions branch from e0c009a to 46a75b9 Compare November 28, 2019 09:55

- name: "Send code coverage report to Codecov.io"
env:
CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@localheinz localheinz force-pushed the feature/github-actions branch 3 times, most recently from 8ca9d4f to 504197e Compare November 28, 2019 10:00
@localheinz localheinz force-pushed the feature/github-actions branch from 504197e to e21e79b Compare November 28, 2019 10:01
@fzaninotto
Copy link
Owner

Please avoid force pushing. The merger can squash the commits when merging the PR.

@localheinz
Copy link
Contributor Author

@fzaninotto @pimjansen

I think this is good for another review!

@localheinz
Copy link
Contributor Author

@fzaninotto @pimjansen

Please make sure to squash the commits on merge!

@localheinz localheinz mentioned this pull request Dec 1, 2019
1 task
@pimjansen pimjansen merged commit d7b25e0 into fzaninotto:next Dec 2, 2019
@localheinz localheinz deleted the feature/github-actions branch December 2, 2019 20:04
@localheinz
Copy link
Contributor Author

Thank you, @fzaninotto and @pimjansen!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants