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.5 KiB

Raw Blame History

name

description

compatibility

metadata

speckit-git-remote

Detect Git remote URL for GitHub integration

Requires spec-kit project structure with .specify/ directory

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

Detect Git Remote URL

Detect the Git remote URL for integration with GitHub services (e.g., issue creation).

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 return empty:

[specify] Warning: Git repository not detected; cannot determine remote URL

Execution

Run the following command to get the remote URL:

git config --get remote.origin.url

Output

Parse the remote URL and determine:

Repository owner: Extract from the URL (e.g., github from https://github.com/github/spec-kit.git)
Repository name: Extract from the URL (e.g., spec-kit from https://github.com/github/spec-kit.git)
Is GitHub: Whether the remote points to a GitHub repository

Supported URL formats:

HTTPS: https://github.com/<owner>/<repo>.git
SSH: git@github.com:<owner>/<repo>.git

Caution

ONLY report a GitHub repository if the remote URL actually points to github.com. Do NOT assume the remote is GitHub if the URL format doesn't match.

Graceful Degradation

If Git is not installed, the directory is not a Git repository, or no remote is configured:

Return an empty result
Do NOT error — other workflows should continue without Git remote information

1.5 KiB Raw Blame History