Skip to content
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

Git sync info #13354

Closed
wants to merge 1 commit into from
Closed

Git sync info #13354

wants to merge 1 commit into from

Conversation

joaomoreno
Copy link
Member

@joaomoreno joaomoreno commented Oct 7, 2016

Proposed alternative to #13313, fixes #8655

@chrmarti @bgashler1 This is what I meant.

image

The tooltip shows instantly, so you can't miss it. We can even render anything in there... like the actual commit IDs and messages in- and outgoing.

@joaomoreno joaomoreno added feature-request Request for new features or functionality git GIT issues labels Oct 7, 2016
@joaomoreno joaomoreno added this to the October 2016 milestone Oct 7, 2016
@mention-bot
Copy link

@joaomoreno, thanks for your PR! By analyzing the history of the files in this pull request, we identified @egamma, @bpasero and @aeschli to be potential reviewers.

@bgashler1
Copy link
Contributor

bgashler1 commented Oct 7, 2016

@joaomoreno I think it's quite useful to show what you're proposing here for information sake (and the problem is probably less likely to occur with this), but I still think having prompt is a good safeguard to prevent first-timers from the unintended consequences of clicking this without reading this or understanding it. It also is making permanent changes to a remote repo's history, which I don't think should be taken lightly, even though it can be reverted with an additional commit. We don't want to hear "VS Code made me do it!" as an excuse for people that are chastised by their peers for pushing things they weren't supposed to.

I do agree though that if we do a prompt, it should have a "Never show this again" checkbox, or it could get tedious. @chrmarti your thoughts?

@chrmarti
Copy link
Contributor

chrmarti commented Oct 7, 2016

@bgashler1 We can't do that with the built-in confirmation dialog from what I see. We could replace it with our regular message box if we're fine with it not being 'blocking' as the confirmation dialog is.

@bgashler1
Copy link
Contributor

@chrmarti that's too bad. I hesitate to use the notification alert. It feels like a dialog would make more sense, since we use that for irreversible actions like closing without saving, Git cleaning, etc... Just my opinion.

@joaomoreno
Copy link
Member Author

@chrmarti @bgashler1

It seems to me that you are not up for discussion on this subject; we've been going back and forward on it for weeks. It started with the suggestion to introduce a confirmation dialog. Here we are today and you haven't budged. So I've just pushed 9601072.

@joaomoreno joaomoreno closed this Oct 10, 2016
@chrmarti
Copy link
Contributor

Thanks @joaomoreno. Happy to discuss further. The important thing for me is that new users can no longer trigger the action without exactly knowing what it will do.

@joaomoreno joaomoreno deleted the git-sync-info branch October 10, 2016 15:41
@github-actions github-actions bot locked and limited conversation to collaborators Mar 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality git GIT issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Git: status bar lacks indication that it will push
5 participants