Template
jmiller
4ebd71abcc
Universal: Auto Version Bump / Version Bump (push) Successful in 11s
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Successful in 11s
Universal: Changelog Validation / Validate CHANGELOG.md (push) Failing after 4s
Branch Policy Check / Verify merge target (pull_request) Successful in 1s
Publish to npm / publish (push) Has been skipped
Universal: PR Check / Branch Policy (pull_request) Successful in 2s
Universal: PR Check / Secret Scan (pull_request) Successful in 5s
Generic: Project CI / Lint & Validate (pull_request) Successful in 19s
Universal: PR Check / Validate PR (pull_request) Successful in 4s
Generic: Standards Compliance / Secret Scanning (push) Successful in 3s
Generic: Standards Compliance / License Header Validation (push) Successful in 4s
Generic: Standards Compliance / Repository Structure Validation (push) Failing after 3s
Generic: Standards Compliance / Coding Standards Check (push) Successful in 4s
Generic: Standards Compliance / Workflow Configuration Check (push) Failing after 5s
Generic: Standards Compliance / Documentation Quality Check (push) Successful in 4s
Generic: Standards Compliance / README Completeness Check (push) Failing after 4s
Generic: Standards Compliance / Line Length Check (push) Has been cancelled
Generic: Standards Compliance / Git Repository Hygiene (push) Successful in 4s
Generic: Standards Compliance / File Naming Standards (push) Has been cancelled
Generic: Standards Compliance / Insecure Code Pattern Detection (push) Has been cancelled
Generic: Standards Compliance / Code Complexity Analysis (push) Has been cancelled
Generic: Standards Compliance / Dead Code Detection (push) Has been cancelled
Generic: Standards Compliance / File Size Limits (push) Has been cancelled
Generic: Standards Compliance / Binary File Detection (push) Has been cancelled
Generic: Standards Compliance / TODO/FIXME Tracking (push) Has been cancelled
Generic: Standards Compliance / Dependency Vulnerability Scanning (push) Has been cancelled
Generic: Standards Compliance / Unused Dependencies Check (push) Has been cancelled
Generic: Standards Compliance / Broken Link Detection (push) Has been cancelled
Generic: Standards Compliance / API Documentation Coverage (push) Has been cancelled
Generic: Standards Compliance / Accessibility Check (push) Has been cancelled
Generic: Standards Compliance / Performance Metrics (push) Has been cancelled
Generic: Standards Compliance / Enterprise Readiness Check (push) Has been cancelled
Generic: Standards Compliance / Repository Health Check (push) Has been cancelled
Generic: Standards Compliance / Terraform Configuration Validation (push) Has been cancelled
Universal: Sync Version on Merge / Propagate README version (push) Has been cancelled
Generic: Project CI / Tests (pull_request) Has been cancelled
Universal: PR Check / Build RC Package (pull_request) Has been cancelled
Universal: PR Check / Report Issues (pull_request) Has been cancelled
Generic: Standards Compliance / Compliance Summary (push) Has been cancelled
Generic: Standards Compliance / Script Integrity Validation (push) Successful in 8s
Generic: Standards Compliance / Version Consistency Check (push) Successful in 50s
Generic: Standards Compliance / Code Duplication Detection (push) Successful in 51s
Co-authored-by: Jonathan Miller <jmiller@mokoconsulting.tech> Co-committed-by: Jonathan Miller <jmiller@mokoconsulting.tech>
Contributing to Template-NPM
We appreciate your interest in contributing to this project! This document provides guidelines for contributing.
Table of Contents
- Code of Conduct
- Getting Started
- How to Contribute
- Development Workflow
- Commit Messages
- Pull Request Process
Code of Conduct
This project adheres to the Contributor Covenant Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to hello@mokoconsulting.tech.
Getting Started
- Fork the repository
- Clone your fork locally
- Set up the development environment
- Create a new branch for your work
How to Contribute
Reporting Bugs
- Use the GitHub issue tracker
- Describe the bug clearly with steps to reproduce
- Include relevant logs, screenshots, or error messages
- Specify your environment (OS, version, etc.)
Suggesting Enhancements
- Use the GitHub issue tracker
- Clearly describe the enhancement and its benefits
- Provide examples of how it would work
Contributing Code
- Pick an issue or create one
- Fork the repository and create a branch
- Make your changes following the project conventions
- Write or update tests as needed
- Submit a pull request
Development Workflow
- Ensure your fork is up to date with the main repository
- Create a feature branch from
main - Make your changes
- Test your changes thoroughly
- Commit your changes with clear messages
- Push to your fork
- Create a pull request
Commit Messages
Follow the conventional commit format:
<type>(<scope>): <subject>
<body>
<footer>
Types: feat, fix, docs, style, refactor, test, chore, ci, build, perf, revert
Example:
feat(docs): add contributing guidelines
Add comprehensive contributing guidelines to help new contributors
understand the development workflow and coding standards.
Pull Request Process
- Update documentation for any new features
- Follow the project's coding style and conventions
- Ensure all tests pass
- Update the CHANGELOG.md with your changes
- Request review from maintainers
- Address any feedback promptly
- Once approved, your PR will be merged
Style Guidelines
- Follow the
.editorconfigsettings - Use tabs for indentation (width: 2 spaces)
- Ensure files end with a newline
- Use LF line endings (except for Windows-specific files)
- Trim trailing whitespace (except in Markdown)
Questions?
If you have questions about contributing, feel free to open an issue or contact the maintainers.
Revision History
| Date | Version | Author | Notes |
|---|---|---|---|
| 2026-01-16 | 0.1.0 | Copilot | Initial contributing guidelines |
Infrastructure Standards
All repositories in the MokoConsulting org follow these conventions:
Release Tags
Every repo maintains 5 standard release channel tags:
development- Active development buildsalpha- Early internal testingbeta- Broader testing / client UATrelease-candidate- Final QA before productionstable- Production release
Branch Protection
mainis protected; onlyjmillercan push directly- All other contributors must use pull requests
- PRs are automatically reviewed by Claude Code
CI/CD
- MokoGIT Actions runs all CI workflows
- GitHub Actions are disabled on mirrored repos
- Workflows live in both
.github/workflows/and.mokogit/workflows/
Update Servers (Joomla)
In manifest <updateservers>, MokoGIT must be priority 1, GitHub priority 2.
Secrets
All repos have GA_TOKEN and GH_TOKEN as Actions secrets for API access.