chore: document latest tag rather than main #77
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SamMorrowDrums
requested review from
Copilot and
toby
and removed request for
Copilot
There was a problem hiding this comment.
Pull Request Overview
This PR updates the installation instructions in the README to remove the explicit reference to the "main" tag and rely on Docker's default behavior, which uses the published "latest" tag.
- Changed docker command in the README to remove the ":main" tag.
- Updated both code blocks where the image reference was specified.
Tip: If you use Visual Studio Code, you can request a review from Copilot before you push from the "Source Control" tab. Learn more
williammartin
approved these changes
Apr 3, 2025
manian0430
pushed a commit
to ChrisLally/github-mcp-server
that referenced
this pull request
Apr 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We now have a published
latestdocker tag that will keep up with actual releases, so we should avoid suggestingmainas it is more likely to be broken or required further testing before rolling out.