Sipke Schoorstra ab3e46bbe2

[codex] Add live server log streaming diagnostics (#7438 )

* 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.

2026-05-11 00:08:52 +02:00

1.7 KiB

Raw Permalink Blame History

name

description

compatibility

metadata

speckit-git-initialize

Initialize a Git repository with an initial commit

Requires spec-kit project structure with .specify/ directory

author	source
github-spec-kit	git:commands/speckit.git.initialize.md

Initialize Git Repository

Initialize a Git repository in the current project directory if one does not already exist.

Execution

Run the appropriate script from the project root:

Bash: .specify/extensions/git/scripts/bash/initialize-repo.sh
PowerShell: .specify/extensions/git/scripts/powershell/initialize-repo.ps1

If the extension scripts are not found, fall back to:

Bash: git init && git add . && git commit -m "Initial commit from Specify template"
PowerShell: git init; git add .; git commit -m "Initial commit from Specify template"

The script handles all checks internally:

Skips if Git is not available
Skips if already inside a Git repository
Runs git init, git add ., and git commit with an initial commit message

Customization

Replace the script to add project-specific Git initialization steps:

Custom .gitignore templates
Default branch naming (git config init.defaultBranch)
Git LFS setup
Git hooks installation
Commit signing configuration
Git Flow initialization

Output

On success:

✓ Git repository initialized

Graceful Degradation

If Git is not installed:

Warn the user
Skip repository initialization
The project continues to function without Git (specs can still be created under specs/)

If Git is installed but git init, git add ., or git commit fails:

Surface the error to the user
Stop this command rather than continuing with a partially initialized repository

1.7 KiB Raw Permalink Blame History