feat: add version subcommand to display build metadata

[joe-ton]

Feature: version Subcommand for GitHub MCP Server CLI

This PR adds a new version subcommand to the GitHub MCP Server CLI, providing build metadata for better visibility and traceability in development and CI environments.

What’s Included

• Adds server version command using Cobra
• Outputs:
  • Semantic version
  • Git commit hash
  • UTC build date

### Build Metadata Injection
go build -ldflags "\ -X main.version=v0.1.0 \ -X main.commit=$(git rev-parse --short HEAD)\ -X main.date=$(date -u +%Y-%m-%d)" \
-o server ./cmd/github-mcp-server
### Example Output
$ ./server version
GitHub MCP Server
Version: v0.1.0
Commit: abc1234
Build Date: 2025-04-04

Perhaps work on Makefiles / automation (build + make) for later.

[joe-ton]

✅ Rebased with main and resolved conflicts.
✅ PR passes local testing.
Let me know if anything else is needed!

[juruen]

@joe-ton

There's already a -v flag to display version info:

 % ./github-mcp-server -v
server version v0.1.0 (270bbf7) 2025-04-05

isn't that enough?

[SamMorrowDrums]

I believe we can add a SetVersionTemplate param to the root cobra command or similar to improve the output, as I agree that the output could be nicer, and I like the format suggested in this PR.

But as @juruen mentioned, the --version flag, and ldflags are already being set in the docker builds and binary builds specified in the .goreleaser file in the repo root.

[joe-ton]

@juruen@SamMorrowDrums

Good point -- I noticed the -v flag after opening the PR. My intent here was improving the clarity and completeness of the build metadata for easier traceability in CI/CD environments. If we're aligned on keeping the simpler flag, I'm happy to refactor the existing -v output using SetVersionTemplate as Sam suggested. Would this work for you both?

[SamMorrowDrums]

Yes, definitely.

[joe-ton]

@SamMorrowDrums@juruen

Implemented version output improvement using SetVersionTemplate. Ready for review and workflow approval. Let me know if any additional tweaks are needed!

[joe-ton]

For easy reproduction and verification, you can use the following:

In project root:

Build:

go build -ldflags "\
-X main.version=v0.1.0 \
-X main.commit=$(git rev-parse --short HEAD) \
-X main.date=$(date -u +%Y-%m-%d)" \
-o server ./cmd/github-mcp-server

Test:

./server --version

[SamMorrowDrums]

@joe-ton I fixed spaces instead of tabs, and because the template command uses a template library, I made use of it - although it doesn't make much difference. The output is the same.

GitHub MCP Server
Version: v0.1.0
Commit: ff3036d
Build Date: 2025-04-15

[SamMorrowDrums]

@joe-ton the tabs not spaces thing for go is important, and you should have go-fmt run on save in your code editor. The Go tools are great, and will save you a bunch of time!

[joe-ton]

@SamMorrowDrums Thanks for accepting the PR. Yes, I need to do go-fmt on my NeoVim config lol Appreciate it!!