تشغيل أي مهارة في Manus بنقرة واحدة

ابدأ الآن

dev-workflow

النجوم٤

التفرعات٦

آخر تحديث٢٩ أبريل ٢٠٢٦ في ٠٢:٤٣

Branches, CI expectations, Composer test/docs, PR hygiene for Contentstack PHP SDK.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

contentstack

contentstack/contentstack-php

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	dev-workflow
description	Branches, CI expectations, Composer test/docs, PR hygiene for Contentstack PHP SDK.

Development workflow – Contentstack PHP SDK

When to use

Setting up locally, opening a PR, or aligning with repository automation.
Answering “how do we run tests?” or “why did the branch check fail?”

Branches

Use feature branches (e.g. feat/..., fix/..., ticket branches).
Release flow is direct development -> master (no staging intermediate branch).
Policy / SCA workflows may run on PRs (see .github/workflows/policy-scan.yml, sca-scan.yml).

Running tests and build

Install: composer install
Tests: composer test or vendor/bin/phpunit (config: phpunit.xml, suite under test/).
Tests may require Contentstack credentials or mocks as documented in test/README.md—do not commit secrets.

Documentation generation

Doctum: composer run generate:docs (see config.php, output per Doctum defaults).

Pull requests

Build/tests pass locally where applicable (composer test).
Follow the code-review skill (skills/code-review/SKILL.md) before merge.
Prefer backward-compatible public API; call out breaking changes and semver.
Update CHANGELOG.md when behavior visible to integrators changes.

References

skills/testing/SKILL.md
skills/code-review/SKILL.md

المزيد من هذا المستودع

نفس المستودع

code-review

contentstack/contentstack-php

PR checklist—API stability, docs, errors, compatibility, dependencies/SCA, tests; Blocker/Major/Minor.

2026-04-074

contentstack-utils

contentstack/contentstack-php

PHP Delivery SDK API—Contentstack::Stack, queries, entries, assets, regions, sync; RTE via Composer package contentstack/utils.

2026-04-074

framework

contentstack/contentstack-php

Composer package, PSR-4 autoload, Doctum docs, PHP version constraints, dev dependencies.

2026-04-074

php-style

contentstack/contentstack-php

PSR-4 layout, namespaces, docblocks, PHP compatibility, src/ structure for this SDK.

2026-04-074

testing

contentstack/contentstack-php

PHPUnit—test/ layout, helpers, constants, coverage output, secrets hygiene.

2026-04-074

name	dev-workflow
description	Branches, CI expectations, Composer test/docs, PR hygiene for Contentstack PHP SDK.

Development workflow – Contentstack PHP SDK

When to use

Setting up locally, opening a PR, or aligning with repository automation.
Answering “how do we run tests?” or “why did the branch check fail?”

Branches

Use feature branches (e.g. feat/..., fix/..., ticket branches).
Release flow is direct development -> master (no staging intermediate branch).
Policy / SCA workflows may run on PRs (see .github/workflows/policy-scan.yml, sca-scan.yml).

Running tests and build

Install: composer install
Tests: composer test or vendor/bin/phpunit (config: phpunit.xml, suite under test/).
Tests may require Contentstack credentials or mocks as documented in test/README.md—do not commit secrets.

Documentation generation

Doctum: composer run generate:docs (see config.php, output per Doctum defaults).

Pull requests

Build/tests pass locally where applicable (composer test).
Follow the code-review skill (skills/code-review/SKILL.md) before merge.
Prefer backward-compatible public API; call out breaking changes and semver.
Update CHANGELOG.md when behavior visible to integrators changes.

References

skills/testing/SKILL.md
skills/code-review/SKILL.md