OpenAPITools/openapi-generator

[REQ][PHP] Add minimal CI config to PHP generators

Open

#11,858 opened on Mar 11, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (7,516 forks)batch import
Client: PHPEnhancement: CI/TestGood First IssueServer: PHPhelp wanted

Repository metrics

Stars
 (26,243 stars)
PR merge metrics
 (Avg merge 9d 1h) (123 merged PRs in 30d)

Description

Is your feature request related to a problem? Please describe.

Recently noticed how many PHP based projects migrates from Travis-CI to GitHub Actions. I didn't try it yet, but after a quick reading I see that GitHub Actions has Ubuntu environment with preinstalled PHP from 7.4 to 8.1, while Travis CI offers Bionic Env with PHP 7.4 only. It can speed up tests significantly I guess.

Since I never used other CI tools but Travis CI, I would ask our community to share their practices regarding PHP CI. If somebody can drop a config to test generated samples under PHP 7.4, 8.0 and 8.1 via GitHub hosted runners I would much appreciate that.

Describe the solution you'd like

  • Remove Travis CI config from current repo and from all PHP based generators samples.
  • Setup GitHub Actions to autotest PHP based generators also add basic config to samples.

Describe alternatives you've considered

Suggest other tool if GitHub Actions doesn't fit.

Additional context

This might be a good first issue for new contributors since you don't need to know Java.

cc @jebentier @dkarlovi @mandrean @jfastnacht @ackintosh @renepardon active PHP contributor @Articus

Contributor guide

Research direction
Study the existing Travis CI config for PHP generators and create a GitHub Actions workflow with matrix strategy for PHP 7.4, 8.0, 8.1.
Tech stack
phpgithub actions
Domain
ci cddevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85