Skip to content

Add timestamp to README #1960

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
hstaudacher wants to merge 1 commit into from
Closed

Add timestamp to README #1960

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
[![Go Report Card](https://goreportcard.com/badge/github.com/github/github-mcp-server)](https://goreportcard.com/report/github.com/github/github-mcp-server)

*Last updated: 2026-02-04*

Comment on lines +3 to +4

Copilot AI Feb 4, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding a static "last updated" timestamp to the README will require manual maintenance and will quickly become outdated. The README.md file is partially auto-generated by the script/generate-docs command (which regenerates sections between automated markers), but this script doesn't update timestamps. This means the timestamp will become inaccurate after the next documentation generation or any other README update.

Consider either:

  1. Removing the timestamp entirely (Git history already tracks when files were last modified)
  2. Implementing automatic timestamp generation in the generateReadmeDocs function in cmd/github-mcp-server/generate_docs.go so it stays current
  3. Using a CI workflow that automatically updates the timestamp on commits

If tracking documentation freshness is important, option 2 would be the most maintainable approach.

Suggested change
*Last updated: 2026-02-04*

Copilot uses AI. Check for mistakes.
# GitHub MCP Server

The GitHub MCP Server connects AI tools directly to GitHub's platform. This gives AI agents, assistants, and chatbots the ability to read repositories and code files, manage issues and PRs, analyze code, and automate workflows. All through natural language interactions.
Expand Down
Loading