docs: Fix GitHub brand notation #20629
Merged
Conversation
This file contains 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
kaos
approved these changes
Feb 29, 2024
| @@ -43,7 +43,7 @@ function git_merge_base() { | |||
| # This prints the tracking branch if set and otherwise falls back to the commit before HEAD. | |||
| # We fall back to the commit before HEAD to attempt to account for situations without a tracking | |||
| # branch, which might include `main` builds, but can also include branch-PR builds, where | |||
| # Travis checks out a specially crafted Github `+refs/pull/11516/merge` branch. | |||
| # Travis checks out a specially crafted GitHub `+refs/pull/11516/merge` branch. | |||
There was a problem hiding this comment.
Travis..?!? Lol, this must be very old, and also a stale comment, as travis have not been used for years (before my time with the project).
There was a problem hiding this comment.
Information about travis is also found elsewhere haha.
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.
During a release, the contents of this directory is synced with our website repo (https://github.com/pantsbuild/pantsbuild.org) to be deployed.Does this mean it's okay to edit the docs file in either the pants repo or the pantsbuild.rog repo?