Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Introduce Phing as build tool for code quality pipeline

未关闭
  • 哪里不对？
#20 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
42/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
php
领域
build-system, testing

调研方向

Start by reading the existing Makefile and GitHub Actions workflow, then check the Composer dependencies and available PHPCS, PHPStan, and PHPUnit commands. Decide how Phing should fit the existing build setup and whether the open questions need maintainer input. Done means a documented Phing setup that runs the agreed quality checks consistently.

由索引模型根据 Issue 内容生成。

描述

enhancement good first issue

Context

Currently there is no automated build pipeline for code quality checks. Running lint, static analysis and tests manually is error-prone and inconsistent across contributors.

Proposal

Introduce Phing as the build tool to orchestrate tasks like:

  • PHP_CodeSniffer (PHPCS) for coding style
  • PHPStan for static analysis
  • PHPUnit tests

A build.xml could look like:

<project name="openapi-php-sdk" default="check">
  <target name="check" depends="lint,test"/>

  <target name="lint">
    <exec command="./vendor/bin/phpcs src/ --standard=PSR12" passthru="true" checkreturn="true"/>
  </target>

  <target name="test">
    <exec command="./vendor/bin/phpunit" passthru="true" checkreturn="true"/>
  </target>
</project>

Open questions

  • Should we enforce PSR-12 strictly or allow some exceptions (e.g. trailing commas)?
  • Do we integrate Phing into the existing Makefile or replace it entirely?
  • Should Phing targets also run inside the GitHub Actions workflow?
主要语言
PHP
星标
20
派生
3
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

openapi/openapi-php-sdk 的其他 Issue

查看 openapi/openapi-php-sdk 的全部 Issue

相似的 Issue

更多 PHP Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。