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

Change Not git repo message #1751

Closed
wants to merge 2 commits into from
Closed

Conversation

@micheleissa
Copy link
Contributor

@micheleissa micheleissa commented Jun 19, 2018

  • Per #1727 change the text of the message.
- Per 1727 change the text of the message.
@grokys
Copy link
Contributor

@grokys grokys commented Jun 19, 2018

Thanks @micheleissa! I'm wondering if we should maybe have two messages: one for when there's no solution opened and one for when there's a solution opened but it's not a git repository? Not sure really, @sguthals what do you think?

@jcansdale
Copy link
Collaborator

@jcansdale jcansdale commented Jun 20, 2018

@grokys,

I'm wondering if we should maybe have two messages: one for when there's no solution opened and one for when there's a solution opened but it's not a git repository?

I think we should do this with another message for when a repository exists but there is no origin remote defined. At the moment users are given no clues as to what's going on.

@grokys
Copy link
Contributor

@grokys grokys commented Jun 20, 2018

Yeah, possibly, but that sounds like a separate PR to me?

@jcansdale
Copy link
Collaborator

@jcansdale jcansdale commented Jun 20, 2018

Yeah, possibly, but that sounds like a separate PR to me?

I just wanted to mention there were a few different things we might want to check for -- eventually. 😄

@micheleissa
Copy link
Contributor Author

@micheleissa micheleissa commented Jun 20, 2018

So will this pr be accepted or not?

@sguthals
Copy link
Contributor

@sguthals sguthals commented Jun 20, 2018

@grokys yes! I agree with:

one for when there's no solution opened and one for when there's a solution opened but it's not a git repository?

@micheleissa Are you up for making that distinction as part of this pr?

@micheleissa
Copy link
Contributor Author

@micheleissa micheleissa commented Jun 20, 2018

@sguthals I can try if it is easy to know there is a an opened non-git solution. I might ask for some directions.

@micheleissa
Copy link
Contributor Author

@micheleissa micheleissa commented Jun 21, 2018

I'm not familiar at all with Xaml so I don't know where to begin..all I know for now is the view GenericNotAGitRepositoryView is using NotAGitRepositoryMessage resource. Could you guys shed some light on that and where and when does this panel even displayed?

@grokys
Copy link
Contributor

@grokys grokys commented Jun 21, 2018

@micheleissa this is handled by the GitHubPaneViewModel:

https://github.com/github/VisualStudio/blob/master/src/GitHub.App/ViewModels/GitHubPane/GitHubPaneViewModel.cs#L396-L407

This piece of code sets the pane's Content property according to whether a repository exists, and it has a clone URL.

For information on how ViewModels are turned into views you might want to look at our developer documentation:

https://github.com/github/VisualStudio/tree/master/docs/developer

In particular:

https://github.com/github/VisualStudio/blob/master/docs/developer/how-viewmodels-are-turned-into-views.md

@micheleissa
Copy link
Contributor Author

@micheleissa micheleissa commented Jun 23, 2018

@grokys thanks. Do I need to check in https://github.com/github/VisualStudio/blob/master/src/GitHub.App/ViewModels/GitHubPane/GitHubPaneViewModel.cs#L396-L407 if a solution open or not?
and also for a msg 'if not a git' repo I think this is handled already.

@grokys
Copy link
Contributor

@grokys grokys commented Jul 5, 2018

@micheleissa yes that's what you'll need to do. You'll want to abstract the "is a solution open?" check into a service so that it can be unit tested.

@StanleyGoldman
Copy link
Contributor

@StanleyGoldman StanleyGoldman commented Apr 16, 2019

Hey @micheleissa are you still interested in working on this?

@micheleissa
Copy link
Contributor Author

@micheleissa micheleissa commented Apr 19, 2019

@StanleyGoldman I might take a look at it this next week. Do you guys have a deadline for it?

@vbarcaru
Copy link

@vbarcaru vbarcaru commented Apr 19, 2019

@meaghanlewis
Copy link
Contributor

@meaghanlewis meaghanlewis commented Apr 19, 2019

No, there is no deadline @micheleissa. Just wondering if you were still interested in completing this work.

@micheleissa
Copy link
Contributor Author

@micheleissa micheleissa commented Apr 21, 2019

@meaghanlewis thank you, I'm trying to re-produce the issue but I can't. Have any of you guys managed to produce it and if so could you tell me how? Thanks again.

@jcansdale
Copy link
Collaborator

@jcansdale jcansdale commented Mar 15, 2020

Closing some very old PRs.

@jcansdale jcansdale closed this Mar 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

7 participants
You can’t perform that action at this time.