Skip to content

[CI] Migrate to GH actions #399

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 30, 2021
Merged

[CI] Migrate to GH actions #399

merged 1 commit into from
Aug 30, 2021

Conversation

ostrolucky
Copy link
Collaborator

Q A
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Related tickets
Documentation
License MIT

No coverage for now, can come later

Copy link
Collaborator

@dbu dbu left a comment

Choose a reason for hiding this comment

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

thanks!

@ostrolucky ostrolucky force-pushed the gh-actions branch 3 times, most recently from 5e3de0c to 76ba153 Compare August 30, 2021 11:28
@ostrolucky ostrolucky marked this pull request as ready for review August 30, 2021 11:36
@ostrolucky ostrolucky force-pushed the gh-actions branch 2 times, most recently from 549b725 to cd875f3 Compare August 30, 2021 12:08
@sagikazarmark
Copy link
Member

Thanks for the PR. Please see my suggestions.

@ostrolucky
Copy link
Collaborator Author

ostrolucky commented Aug 30, 2021

Thanks for review @sagikazarmark. I would say subjective suggestions, but I've implemented them. Just FYI, I took most of the structure over from https://github.com/doctrine/DoctrineBundle/tree/2.4.x/.github/workflows

@dbu
Copy link
Collaborator

dbu commented Aug 30, 2021

we should adjust the README.md as well, to have the badge and link from github actions rather than travis.

the badge url is https://github.com/php-http/HttplugBundle/actions/workflows/continuous-integration.yml/badge.svg and i would link that to https://github.com/php-http/HttplugBundle/actions/

@sagikazarmark
Copy link
Member

Thanks for making the changes @ostrolucky ! Yes, I guess they are subjective, but that's how things are implemented in the projects I maintain (Twirp, Guzzle, MoneyPHP) and they worked well for the last couple years, so I prefer keeping them consistent (unless there are reasons not to of course).

No coverage for now, can come later
@ostrolucky
Copy link
Collaborator Author

All good?

Copy link
Collaborator

@dbu dbu left a comment

Choose a reason for hiding this comment

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

looks good to me, thanks

@dbu
Copy link
Collaborator

dbu commented Aug 30, 2021

should we put an editorconfig based on https://github.com/twirphp/twirp/blob/master/.github/.editorconfig into the .github folder? we have those at top level in our company projects and they are useful to help with consistent whitespace (and explicitly define the rules)

@ostrolucky
Copy link
Collaborator Author

Rather top level. But separate changeset please

@ostrolucky ostrolucky merged commit 1ba9f58 into master Aug 30, 2021
@sagikazarmark
Copy link
Member

Having a top level editorconfig file is always a good idea and we should already have those in all php-http repos. Having one in .github helps configuring how editors should behave within that folder. I'd say 4 spaces should be the default everywhere, but GitHub workflows are indentated with 2 spaces everywhere (docs, examples), so limiting 2 spaces to .github makes sense.

@dbu dbu deleted the gh-actions branch September 21, 2021 08:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants