Skip to content

/ VisualStudio

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

Jump to bottom

No success message returned after publishing local repo. #672

Closed
femisimon opened this issue Nov 8, 2016 · 0 comments
Closed

No success message returned after publishing local repo. #672

femisimon opened this issue Nov 8, 2016 · 0 comments
Assignees
@paladique
Labels
bug
Projects
2.2.0.8

Comments

@femisimon
Copy link

@femisimon femisimon commented Nov 8, 2016

Visual Studio Community
GHfVS - 2.0.15.1

A user-friendly message is expected to be returned when a user successfully publish a local repo on Visual Studio.
Currently, no friendly message is returned for successfully publishing a local repo.

Steps to reproduce

  • Create a local repo from the local git section of the Team Explorer pane.
  • Click on the home icon > Sync
  • Publish using GitHub

Actual - Local repo is published with navigation to Wiki, Pulse, Pull request, etc

Expect - Friendly successful message with navigation to Wiki, Pulse, Pull request, etc
@femisimon femisimon added the bug label Nov 8, 2016
@grokys grokys mentioned this issue Feb 2, 2017
Closed
@grokys grokys added this to Not Started in 2.2.0.8 Feb 2, 2017
@paladique paladique mentioned this issue Feb 13, 2017
Merged
@grokys grokys moved this from Not Started to In Progress in 2.2.0.8 Feb 16, 2017
@grokys grokys closed this in #851 Feb 24, 2017
@paladique paladique moved this from In Progress to Done in 2.2.0.8 Feb 24, 2017
@grokys grokys mentioned this issue Jan 25, 2018
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@paladique paladique

Labels
bug
Projects
2.2.0.8
Done
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@paladique @femisimon
You can’t perform that action at this time.