-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
New release #567
New release #567
Conversation
Show the terminal/TTY based prompts when there is no desktop/GUI sessions present for GitHub. Currently the Bitbucket and Microsoft auth stacks correctly detect the lack of a desktop session and use terminal prompts - GitHub does not. Without this change, SSH-ing in to a machine we'd still try and show a UI prompt where there is no way to interact with it!
The Debian package build script incorrectly copies the containing directory to the destination tree rather than just the contents recursively. This means we end up with: usr └── local ├── bin │ ├── Atlassian.Bitbucket.UI -> ../share/gcm-core/Atlassian.Bitbucket.UI │ ├── git-credential-manager-core -> ../share/gcm-core/git-credential-manager-core │ └── GitHub.UI -> ../share/gcm-core/GitHub.UI └── share └── gcm-core ** ---> └── Release ├── Atlassian.Bitbucket.UI ├── git-credential-manager-core ├── GitHub.UI ├── libHarfBuzzSharp.so ├── libSkiaSharp.so └── NOTICE ..rather than: usr └── local ├── bin │ ├── Atlassian.Bitbucket.UI -> ../share/gcm-core/Atlassian.Bitbucket.UI │ ├── git-credential-manager-core -> ../share/gcm-core/git-credential-manager-core │ └── GitHub.UI -> ../share/gcm-core/GitHub.UI └── share └── gcm-core ├── Atlassian.Bitbucket.UI ├── git-credential-manager-core ├── GitHub.UI ├── libHarfBuzzSharp.so ├── libSkiaSharp.so └── NOTICE Since the symlinks are wrong, the installation is broken.
Remove the symlinks to the GitHub and Bitbucket UI helpers in /usr/local/bin. These are not required to have the core GCM application locate the helpers and just create more noise in the user's $PATH.
With the ongoing work to migrate GCM to its new org, we're taking the opportunity to update our references to GCM Core/GCM-Core in documentation to GCM. Note that this change is limited to documentation only - executables and assemblies will be updated at a later time.
Show GitHub terminal prompts when no GUI session
Replacing references to microsoft/Git-Credential-Manager-Core with references to GitCredentialManager/git-credential-manager.
Update references to aka.ms/gcmcore-* to aka.ms/gcm/*.
Drop "Core" from the social banner image
Fix Debian package build script copy command
The CodeQL Results task has been hanging in Pull Requests in our new repo. Planning to remove and re-add via the GitHub UI in the hopes that will make the task work as expected.
workflows: remove CodeQL
Re-adding CodeQL to ensure all checks work as expected in new org/repo.
workflows: add CodeQL
Remove 'core' from docs
fixes #424
fixes #189
TODO include in GitHub actions etc setup, e.g. https://josh-ops.com/posts/github-code-coverage/, once microsoft/vstest#1811 is fixed
Co-authored-by: Matthew John Cheetham <[email protected]>
Co-authored-by: Matthew John Cheetham <[email protected]>
Co-authored-by: Matthew John Cheetham <[email protected]>
Batch of documentation fixes
Fix a MD table that was not rendering correctly.
Add basic support for generating code coverage reports
small formatting issues in uninstall section for linux.
Fix setx command
Update README.md
Update the new issue templates with the extra required WSLENV environment variable that is required for passing trace envars to the Windows host.
Update issue template for WSL tracing
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 think 538 and 539 are all the code changes in this release?
Whoops! I may have gone a little overboard. Should I remove the additional changes I added? |
Not an issue really. I tend to keep the release notes only with code or behavioural changes however. |
Sounds good - noted for the future. |
Changes: