ab3e46bbe2
* Add live server logs Spec Kit plan * Implement live server logs diagnostics module * Add server log sources and redaction hardening * Add diagnostics unit tests * Harden server log hub subscriptions * Secure server log hub permissions * Validate server log filter updates * Add diagnostics logger and source tests * Add diagnostics integration test project * Add multi-source diagnostics provider coverage * Broadcast server log source changes * Document diagnostics server log streaming * Add diagnostics sample host wiring * Record diagnostics validation results * Address server log PR feedback * Rename diagnostics module to server logs * Add server logs shell feature * Make server logs shell options bindable * Accept read wildcard for server logs * Align server logs authorization with API patterns * Update CShells structure and logging levels, add diagnostics module * Rename PostgreSql shell feature classes for consistency * Switch from Sqlite to PostgreSQL for workflow and identity persistence, add QuartzPostgreSql configuration * Refactor server logs into diagnostics structured logs (#7440) * Specify diagnostics structured logs refactor * docs: clarify structured logs spec * docs: plan diagnostics structured logs * docs: add diagnostics structured logs tasks * refactor: rename server logs to diagnostics structured logs * Refactor PostgreSql persistence features to use centralized entity model handler registration. * Refactor EFCore persistence features to centralize entity model handler registration for MySql, Sqlite, and Oracle providers. * Integrate structured logs by renaming server logs, adjusting appsettings, and updating project references. * Switch from PostgreSQL to Sqlite for workflow and identity persistence, update appsettings configuration.
52 lines
1.8 KiB
Markdown
52 lines
1.8 KiB
Markdown
---
|
|
description: Validate current branch follows feature branch naming conventions
|
|
---
|
|
|
|
|
|
<!-- Extension: git -->
|
|
<!-- Config: .specify/extensions/git/ -->
|
|
# Validate Feature Branch
|
|
|
|
Validate that the current Git branch follows the expected feature branch naming conventions.
|
|
|
|
## Prerequisites
|
|
|
|
- Check if Git is available by running `git rev-parse --is-inside-work-tree 2>/dev/null`
|
|
- If Git is not available, output a warning and skip validation:
|
|
```
|
|
[specify] Warning: Git repository not detected; skipped branch validation
|
|
```
|
|
|
|
## Validation Rules
|
|
|
|
Get the current branch name:
|
|
|
|
```bash
|
|
git rev-parse --abbrev-ref HEAD
|
|
```
|
|
|
|
The branch name must match one of these patterns:
|
|
|
|
1. **Sequential**: `^[0-9]{3,}-` (e.g., `001-feature-name`, `042-fix-bug`, `1000-big-feature`)
|
|
2. **Timestamp**: `^[0-9]{8}-[0-9]{6}-` (e.g., `20260319-143022-feature-name`)
|
|
|
|
## Execution
|
|
|
|
If on a feature branch (matches either pattern):
|
|
- Output: `✓ On feature branch: <branch-name>`
|
|
- Check if the corresponding spec directory exists under `specs/`:
|
|
- For sequential branches, look for `specs/<prefix>-*` where prefix matches the numeric portion
|
|
- For timestamp branches, look for `specs/<prefix>-*` where prefix matches the `YYYYMMDD-HHMMSS` portion
|
|
- If spec directory exists: `✓ Spec directory found: <path>`
|
|
- If spec directory missing: `⚠ No spec directory found for prefix <prefix>`
|
|
|
|
If NOT on a feature branch:
|
|
- Output: `✗ Not on a feature branch. Current branch: <branch-name>`
|
|
- Output: `Feature branches should be named like: 001-feature-name or 20260319-143022-feature-name`
|
|
|
|
## Graceful Degradation
|
|
|
|
If Git is not installed or the directory is not a Git repository:
|
|
- Check the `SPECIFY_FEATURE` environment variable as a fallback
|
|
- If set, validate that value against the naming patterns
|
|
- If not set, skip validation with a warning |