Description
Since extensible-nav was enabled by default, extend-repo-tabs changes the repository navigation label from GitHub's native Pull requests to Pulls:
|
function init(): void { |
|
overrideTab('pull-requests', {label: 'Pulls'}); |
|
overrideTab('security-and-quality', {demoted: true}); |
|
overrideTab('insights', {demoted: true}); |
Could Refined GitHub preserve the native Pull requests label, or make this specific shortening independently configurable?
Pulls is less explicit and inconsistent with the wording used elsewhere in GitHub. Disabling all of extend-repo-tabs is a broad workaround because it also removes useful behavior such as repository-tab counters and demotion of empty or rarely used tabs.
Current label: Pulls
Expected label: Pull requests
Related changes:
Example URLs
https://github.com/refined-github/refined-github
Description
Since
extensible-navwas enabled by default,extend-repo-tabschanges the repository navigation label from GitHub's native Pull requests to Pulls:refined-github/source/features/extend-repo-tabs.tsx
Lines 71 to 74 in 53186f2
Could Refined GitHub preserve the native Pull requests label, or make this specific shortening independently configurable?
Pullsis less explicit and inconsistent with the wording used elsewhere in GitHub. Disabling all ofextend-repo-tabsis a broad workaround because it also removes useful behavior such as repository-tab counters and demotion of empty or rarely used tabs.Current label: Pulls
Expected label: Pull requests
Related changes:
extend-repo-tabs- New feature #9902extensible-nav- Enable by default #10010Example URLs
https://github.com/refined-github/refined-github
I had to remove the hotfix as it caused issues for some people (#10053) but later this week I will:
Until then you can continue to use and tweak the CSS above.