DocumentationEnterprise checks
Enterprise checks
Warestack’s enterprise-grade governance is built on extensive research analyzing policies from leading companies.
Enterpirse checks table
| Description | Company | Type | Context |
|---|---|---|---|
Issue titles should be short and clear. | Warestack | Issue | Style Standards |
Issues must include a detailed description. | Warestack | Issue | Communication |
Each issue must have at least one assignee. | Warestack | Issue | Workflow |
Issues must have at least two labels. | Warestack | Issue | Workflow |
Commit messages should follow the conventional format (feat/fix/docs/etc). | Warestack | Pull Request | Style Standards |
Commit messages must clearly describe the change. | Warestack | Pull Request | Style Standards |
Split large PRs (>400 lines) into smaller ones. | Google (Chromium) | Pull Request | Code Quality |
Issue titles should be short and clear. | Warestack | Issue | Style Standards |
Code owner approval is required for certain areas. | Kubernetes | Pull Request | Review Process |
Each PR should focus on one logical change only. | Pull Request | Code Quality | |
Issues must include a detailed description. | Warestack | Issue | Communication |
Require approval from code owners for owned components. | Google (Chromium) | Pull Request | Review Process |
Keep PRs small for easier review (~200–300 lines). | Shopify | Pull Request | Code Quality |
No deployments allowed during weekends. | Warestack | Deployment Review | Deployment Safety |
All required CI tests must pass before merging. | Google (TensorFlow) | Pull Request | CI/CD |
All changes must include tests and updated docs. | Kubernetes | Pull Request | Code Quality |
Each issue must have at least one assignee. | Warestack | Issue | Workflow |
Block merging unless all required CI checks pass. | GitHub | Pull Request | CI/CD |
Reviewers should respond within one business day. | Pull Request | Review Process | |
Commit messages should follow the conventional format (feat/fix/docs/etc). | Warestack | Pull Request | Style Standards |
At least two approvals are required for some PRs. | Google (Chromium) | Pull Request | Review Process |
Include a simple test plan showing how to verify the change. | Meta (Facebook) | Pull Request | Communication |
Issues must have at least two labels. | Warestack | Issue | Workflow |
New features or fixes must include tests. | Google (TensorFlow) | Pull Request | Code Quality |
Security-sensitive changes need an extra security review. | Kubernetes | Pull Request | Security |
Deployment reviews cannot be skipped. | Warestack | Deployment Review | Deployment Safety |
Keep PRs small (around 100 lines). | Pull Request | Code Quality | |
PR descriptions must explain what and why the change is made. | Shopify | Pull Request | Communication |
Performance-related changes must include benchmarks. | Kubernetes | Pull Request | Code Quality |
Commit messages must clearly describe the change. | Warestack | Pull Request | Style Standards |
All code changes must be reviewed and approved by another engineer. | Amazon (AWS) | Pull Request | Review Process |
All review comments must be resolved before merging. | GitHub | Pull Request | Review Process |
Changes must stay backward compatible or provide migration notes. | Kubernetes | Pull Request | Code Quality |
Deployments must be reviewed by another team member. | Warestack | Deployment Review | Deployment Safety |
Every change must be reviewed by another engineer. | Google (TensorFlow) | Pull Request | Review Process |
All contributors must sign the Contributor License Agreement (CLA). | Meta (React) | Pull Request | Governance |
All comment threads must be resolved before merging. | Microsoft (Azure DevOps) | Pull Request | Review Process |
Workflows must not contain hardcoded secrets. | Warestack | Workflow Run | Security |
Follow TypeScript coding standards and best practices. | Microsoft (TypeScript) | Pull Request | Style Standards |
All commits must include a DCO sign-off line. | Linux Foundation (CNCF) | Pull Request | Governance |
PRs should be linked to related issues or tickets. | Apache (Hadoop) | Pull Request | Workflow |
Workflows must finish within the set time limit. | Warestack | Workflow Run | CI/CD |
💡 TIP — You can create and manage checks either directly in a repo’s YAML file or through our dashboard.
Last updated on