Git Branch Name Validator
Validate Git branch names according to Git naming conventions
### Git Branch Name Validator
This tool validates Git branch names according to Git's naming conventions and best practices.
**Git Branch Naming Rules:**
- Cannot contain: `~ ^ : space tab newline ? * [ \`
- Cannot begin or end with `/`
- Cannot have consecutive slashes `//`
- Cannot end with `.lock`
- Cannot contain `..` or `@{`
- Maximum length (typically 255 chars for filesystem compatibility)
- Cannot be a reserved branch name (HEAD, main, master)
**Common Branch Naming Conventions:**
- **feature/** - New features
- **bugfix/** - Bug fixes
- **hotfix/** - Urgent production fixes
- **release/** - Release preparation
- **develop/** - Development branch
- **test/** - Testing branches
- **docs/** - Documentation updates
- **refactor/** - Code refactoring
**Example Valid Names:**
- `feature/user-authentication`
- `bugfix/login-error`
- `hotfix/security-patch-001`
- `release/v1.2.3`
**Example Invalid Names:**
- `feature user auth` (contains spaces)
- `feature//double-slash` (consecutive slashes)
- `.lock-branch` (starts with dot)
- `feature/.lock` (ends with .lock)
**Use Cases:**
- Validate branch names before creation
- Enforce team naming conventions
- Pre-commit hooks for branch naming
- CI/CD pipeline validation
- Code review automation
API Documentation
Request Endpoint
POST /en/api/tools/git-branch-validator
Request Parameters
| Parameter Name | Type | Required | Description |
|---|---|---|---|
| branchName | text | Yes | - |
| allowCustomPrefixes | checkbox | No | Allow branch names without standard prefixes |
| enforceConvention | checkbox | No | Require branch names to follow naming conventions |
| reservedNames | text | No | Branch names that are reserved (comma-separated) |
| maxLength | number | No | Maximum length for branch names (filesystem compatibility) |
| allowedPrefixes | text | No | Valid branch name prefixes (comma-separated, end with /) |
Response Format
{
"key": {...},
"metadata": {
"key": "value"
},
"error": "Error message (optional)",
"message": "Notification message (optional)"
}
JSON Data:
JSON Data
AI MCP Documentation
Add this tool to your MCP server configuration:
{
"mcpServers": {
"elysiatools-git-branch-validator": {
"name": "git-branch-validator",
"description": "Validate Git branch names according to Git naming conventions",
"baseUrl": "https://elysiatools.com/mcp/sse?toolId=git-branch-validator",
"command": "",
"args": [],
"env": {},
"isActive": true,
"type": "sse"
}
}
}
You can chain multiple tools, e.g.: `https://elysiatools.com/mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp`, max 20 tools.
If you encounter any issues, please contact us at [email protected]