Change to "Featured Repositories" #12
Merged
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.
What was changed
I revised the contents of the "Pinned" section and renamed it to "Featured Repositories"
Why?
On Tuesday, we merged PR #11, which provided a workaround for the six-item limit that GitHub imposes on the pinned repositories section. Essentially, we created our own "Pinned" section and removed the one provided by GitHub.
Unfortunately, we discovered that this had the side effect of enabling a "popular repositories" section, which includes an archived repo. GitHub doesn't allow disabling that section—the only remedy is to bring back the "Pinned" section, which I will request separately since it can't be done through a PR.
This PR retitles the "Pinned" section in the README as "Featured Repositories" to avoid confusion with the soon-to-return "Pinned" section. It also removes two items from the current one:
sdk-core(since that is generally not intended for application developers) andtemporal(since that will be in the "Pinned" section). Finally, it moves theclirepo to the bottom-right so that it follows the list of SDKs and will be closer to thetemporalrepo once that is re-pinned.Checklist
How was this tested:
I tested this in Safari, using every one of the themes provided by GitHub (both light and dark mode). I did not test this in other browsers, since this is a change to content, not implementation. It is simply a variation on the previous PR, which I did test in both Chrome and Firefox.