-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Adding Publish to Essentials extension #2360
Conversation
co-authored-by: Jamie Cansdale <[email protected]>
# Conflicts: # src/GitHub.VisualStudio.16/source.extension.vsixmanifest
Use same colors and layout.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something I noticed, do we need a ParentSection
co-authored-by: Jamie Cansdale <[email protected]>
co-authored-by: Jamie Cansdale <[email protected]>
The view already handles this, showing: "Repository created successfully".
This would causes issues when the full extension is also installed. It wouldn't know which version of GitHub.Resources.dl to use.
co-authored-by: Jamie Cansdale <[email protected]>
co-authored-by: Jamie Cansdale <[email protected]>
46fe863 to
b4a400b
Compare
|
We seem to have an issue with the
I was hoping to avoid special casing the color themes by using the build in The image used on We should be using the same image! 😕 |
Couldn't get CrispImage to work for automatic coloring of the Blue theme.
When a user Add/Changes Account, automatically change the host drop-down.
This is surprising. I wonder if you somehow ended up with two versions installed (this can happen after the extension name change). How did you install this version for testing?
I've fixed it so that after you I hope the unexpected behavior was it not being automatically selected, rather than it not appearing in the list at all. |
|
@jcansdale this looks good to me! I'm not experiencing the problems I was previously. Perhaps I didn't notice the account picker before. One small thing that I noticed was that for GitHub repositories the repo name was autofilled, but for GHE it wasn't. |
Only load GitHub.Exports when composition container is created.
This avoids loading the GitHub.Extensions and GitHub.Exports assemblies.
I'm guessing the issue is here, but I don't understand exactly what's going wrong: This will have been a long standing issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've check and double checked. It seems to be working well. LGTM!







Add
Publish to GitHubsection toTeam Explorer - Synchronizationpage:When
Publish to GitHubbutton is clicked:When user opens the
Team Explorer - Synchronizationpage, onlyGitHub.VisualStudio.16will be loaded:How to test
Add to Source Control > GitPublish to GitHubbuttonPrivate(if you don't want your test repository to be publicly visible)PublishbuttonRepository created successfullymessageSyncbutton