Update README.md - #54
Open
xiaunknown116-del wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Here is your complete, production-ready ecosystem layout. It contains the unified workflow file alongside the structural configurations required to natively execute layout formatting and test evaluation processes inside your engineering pipelines.
🏛️ Complete Repository Update
apex-platform-engine/
├── .github/
│ └── workflows/
│ └── pr-gate.yml # Unified Status Gate Workflow (Live Multi-Channel Metrics)
├── .prettierrc # Prettier Layout Standards Engine Configuration
├── package.json # Project Manifest & Vitest Coverage Script Map
├── tsconfig.json # TypeScript Compiler Constraints
└── vitest.config.ts # Test Engine & JSON Summary Coverage Exporter
🚨 1. The Production Workflow (.github/workflows/pr-gate.yml)
Create this file to completely orchestrate file filtering, auto-formatting, type validation, coverage parsing, and multi-channel notification dispatches.
name: Pull Request Quality Gateon:
pull_request:
branches:
- main
paths-ignore:
- "README.md"
- ".gitignore"
- "docs/**"
jobs:
quality_check:
name: Code Quality & Testing Suite
runs-on: ubuntu-latest
permissions:
contents: write # Crucial requirement to allow auto-commits to the branch
steps:
- name: Checkout Code Base
uses: actions/checkout@v4
with:
fetch-depth: 0
ref: ${{ github.head_ref }} # Check out the actual head branch instead of the merge commit
🎨 2. Code Style Configurations (.prettierrc)
Place this configuration file at the root level of your project directory to dictate structural formatting parameters natively:
{
"semi": true,
"trailingComma": "none",
"singleQuote": false,
"tabWidth": 2,
"printWidth": 100,
"bracketSpacing": true,
"arrowParens": "always"
}
🧪 3. Vitest Exporter Integration (vitest.config.ts)
Ensure your testing framework configures and exports the json-summary coverage metric database consumed by the step pipeline:
import { defineConfig } from "vitest/config";
export default defineConfig({
test: {
coverage: {
provider: "v8", // or 'istanbul'
reporter: ["text", "json-summary"],
reportOnFailure: true,
thresholds: {
lines: 80, // Optional: Fails test execution if total coverage dips below 80%
functions: 80,
branches: 80
}
}
}
});
📦 4. Application Dependency Map (package.json)
Ensure your test target keys inside your manifest scripts are configured to enable coverage tracking correctly:
{
"name": "apex-platform-engine",
"version": "1.0.0",
"scripts": {
"test": "vitest run",
"test:coverage": "vitest run --coverage"
},
"devDependencies": {
"@vitest/coverage-v8": "^2.0.0",
"prettier": "^3.0.0",
"typescript": "^5.0.0",
"vitest": "^2.0.0"
}
}
If you're ready to deploy, let me know: