github-starred/git-touch
2
0
Fork 0
mirror of https://github.com/pd4d10/git-touch.git synced 2026-03-12 02:06:17 -05:00
Code Issues 88 Packages Projects Releases 18 Wiki Activity

Option to make account primary #55

New Issue
Closed
opened 2025-10-31 17:04:46 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-10-31 17:04:46 -05:00
Owner
Copy Link

Originally created by @shreyas1599 on GitHub (May 8, 2020).

@pd4d10 Doesn't seem too hard. I'd just have to use a ReorderableList. I'll open a PR for this if it's alright with you.

Originally created by @shreyas1599 on GitHub (May 8, 2020). @pd4d10 Doesn't seem too hard. I'd just have to use a `ReorderableList`. I'll open a PR for this if it's alright with you.
GiteaMirror commented 2025-10-31 17:04:47 -05:00
Author
Owner
Copy Link

@shreyas1599 commented on GitHub (Feb 4, 2021):

I think it's better to have an option to make an account primary so it opens by default while opening the app. (the intention of using reorder able list was to move the frequently used accounts to the top). Making an account primary seems a better way to do it.

@shreyas1599 commented on GitHub (Feb 4, 2021): I think it's better to have an option to make an account primary so it opens by default while opening the app. (the intention of using reorder able list was to move the frequently used accounts to the top). Making an account primary seems a better way to do it.
GiteaMirror commented 2025-10-31 17:04:47 -05:00
Author
Owner
Copy Link

@shreyas1599 commented on GitHub (Feb 4, 2021):

Looks like auth.activeAccount already solves this. But it is not persistent. Login screen reopens if you force close and open the app. Should we just write it into shared prefs?

(Eg: On popular apps that support multiple accounts, opening the last used account is the way its done instead of asking the user to select from the list of accounts)

@pd4d10 Is this fine or do you have an alternative suggestion?

@shreyas1599 commented on GitHub (Feb 4, 2021): Looks like `auth.activeAccount` already solves this. But it is not persistent. Login screen reopens if you force close and open the app. Should we just write it into shared prefs? _(Eg: On popular apps that support multiple accounts, opening the last used account is the way its done instead of asking the user to select from the list of accounts)_ @pd4d10 Is this fine or do you have an alternative suggestion?
GiteaMirror commented 2025-10-31 17:04:47 -05:00
Author
Owner
Copy Link

@pd4d10 commented on GitHub (Feb 4, 2021):

opening the last used account

OK, I think it's a good idea

@pd4d10 commented on GitHub (Feb 4, 2021): > opening the last used account OK, I think it's a good idea
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
gitea
help wanted
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/git-touch#55
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?