11/30/2023 0 Comments Github desktop no sync button![]() There is a fundamental UX flaw that leads to really messy history which has been voiced by "many" that has been patched rather than addressed in full. But what are we defending? The simplicity of one button? Screen realestate? Design ego? I'm confused. Great response, I certainly see it from your point of view also. If you aren’t logged into GitHub, then we’ll prompt for you to login. If you haven’t published a repository or branch, this is where you’ll complete that action. It'll also give us a place to indicate that a background fetch is underway (we'll spin the sync arrows) We considered using 'fetch' but we then decided to add the 'Last fetched.' subtitle to all button states as a way of indicating that we do perform background fetches. ![]() We've used 'Refresh' as the terminology here. In the scenario where the client thinks you're neither ahead nor behind we'll offer to refresh the repository (a fetch). We might consider updating the button text in this state to something like 'Pull and merge'. Instead we'll leave that action to the user so that we'll never push a result that they're not comfortable with. This is similar to what Sync does today except we will do a pull and merge but we will not automatically push that merge commit. If you’re both ahead and behind, we’ll make you do a pull before giving you the ability to push. If your branch has fallen behind the remote we’ll give you the option to pull. If the user opts out the sync button state will have updated to reflect the now-known fact that the remote is ahead. If this fails (non-fast-forward) we'll present the user with information about why and offer to do a pull. If your branch has commits not yet on the remote we’ll give you the option to push. Note that this concept assumes that we keep background fetching in TNG:9000 as we'll need to reflect changes to the remote. Additionally in the case of errors we'll be able to present the underlying error as received from Git to the user (for them to Google). We've opted for using Git terminology primarily so that the button text is something users can throw into Google in order to understand what the action does. In essense we'll present the action that would be taken by a sync button. We've taken another approach by replacing the ambiguous sync button with a contextual button that changes from “Push,” “Pull,” and “Publish” based on how far or ahead you are from the remote branch. The most current thinking being that we'd keep it but with some sort of combo/dropdown so that users could explicitly pull or explicitly push. It doesn't work so well for the remainder of users and various suggestions have been made over the years on how to address this. We believe that it currently serves two groups of users very well, the first being those who deeply understand Git and realize what it's doing and the second is those users who have deep trust in the app and doesn't care all that much about its inner workings. There's nothing else.A very common feedback with the current clients has been that the sync button is scary. ![]() The Github website also just shows the 2 repositores I had created at the very beginning, intialized with a readme.md. However, now that I'm on another (ubuntu) computer and wanted to clone the 2 repositories on this, it appears that none of my commits were ever pushed to Github.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |