deploy-commit-sha

Display the deployed Git commit SHA on a web page.

Updated Mar 29, 2026

Search Tags:#versioning #deployment #web-ui #server-startup #build-verification #commit-sha

Ready to run

npx skills add https://github.com/doolin/dave-skills --skill deploy-commit-sha

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deploy-commit-sha
Source: https://github.com/doolin/dave-skills/tree/main/skills/deploy-commit-sha
Command: npx skills add https://github.com/doolin/dave-skills --skill deploy-commit-sha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill lets you visibly verify the exact deployed git commit by displaying the SHA on a web page.

Core Features & Use Cases

Deploy-time SHA generation into a version.json during packaging.
Server-side injection of the SHA into the HTML at startup.
Optional metadata embedding or fallback to 'dev' for local development.

Quick Start

Tell your app to generate and render the current commit SHA on its UI.

Frequently Asked Questions about deploy-commit-sha

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I display the deployed git commit SHA on a web page?▼

To display the deployed git commit SHA on a web page, your deployment pipeline writes the SHA to a version.json file during packaging, and server startup code replaces an HTML placeholder with the short SHA to verify the exact running code version.

What does showing a commit SHA on a live web page solve for release verification?▼

Showing a commit SHA on a live web page solves release verification ambiguity by letting you visibly audit and debug exactly which code version is running in any environment, preventing confusion during deployment tracking across pipelines.

Can I use this commit SHA injection approach for serverless functions?▼

Yes, you can use this commit SHA injection approach for serverless functions. The technique applies to both web apps and serverless functions by generating a version.json at build time and injecting the short SHA at startup.

How do I show a local development fallback when no commit SHA exists?▼

To show a local development fallback when no commit SHA exists, the startup-time code replaces the HTML placeholder with the string 'dev' instead of the 7-character short SHA, ensuring the UI always displays a valid version indicator.

What is the best way to verify which code version is running across deploy pipelines?▼

The best way to verify which code version is running across deploy pipelines is generating a version.json file during packaging and injecting the short commit SHA into the web UI at startup for immediate visual auditing and debugging.