-
Notifications
You must be signed in to change notification settings - Fork 59.8k
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.
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
[GitHub Desktop] Disabling repo indicators feature #1203
Labels
content
This issue or pull request belongs to the Docs Content team
help wanted
Anyone is welcome to open a pull request to fix this issue
Comments
janiceilene
added
content
This issue or pull request belongs to the Docs Content team
core
help wanted
Anyone is welcome to open a pull request to fix this issue
labels
Nov 9, 2020
github-actions
bot
added
the
triage
Do not begin working on this issue until triaged by the team
label
Nov 9, 2020
janiceilene
removed
the
triage
Do not begin working on this issue until triaged by the team
label
Nov 13, 2020
3 tasks
This was referenced Apr 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
content
This issue or pull request belongs to the Docs Content team
help wanted
Anyone is welcome to open a pull request to fix this issue
Anyone is welcome to open a PR!
Use this Desktop issue, Support disabling repository indicators, to understand the context of this change. Download the current beta version of Desktop to take any screenshots.
This will require an updated image for both windows and mac, because it's a change in the settings (which have different names in each OS).
Audience: Every Desktop user will come across this updated tab if they go into the settings at all. The new tab is particularly relevant for people who work on underpowered machines or who have a ton of repositories in Desktop and there are performance concerns related to the background operations of fetching to update these indicators.
In Configuring basic settings:
The text was updated successfully, but these errors were encountered: