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

@joe-ton

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

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

isn't that enough?

I believe we can add aSetVersionTemplate 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.

@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?

Yes, definitely.

@SamMorrowDrums@juruen

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

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

@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 ServerVersion: v0.1.0Commit: ff3036dBuild Date: 2025-04-15

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

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