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

New release #567

Merged
merged 37 commits into from
Dec 10, 2021
Merged

New release #567

merged 37 commits into from
Dec 10, 2021

Conversation

mjcheetham and others added 30 commits November 17, 2021 14:02
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
Update gcm-test@example.com to gcm@example.com.
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.
Re-adding CodeQL to ensure all checks work as expected in new org/repo.
Co-authored-by: Matthew John Cheetham <mjcheetham@outlook.com>
Co-authored-by: Matthew John Cheetham <mjcheetham@outlook.com>
Co-authored-by: Matthew John Cheetham <mjcheetham@outlook.com>
Fix a MD table that was not rendering correctly.
mjcheetham and others added 7 commits November 25, 2021 13:25
Add basic support for generating code coverage reports
small formatting issues in uninstall section for linux.
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
Copy link
Collaborator

@mjcheetham mjcheetham left a 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?

@ldennington
Copy link
Contributor Author

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?

@mjcheetham
Copy link
Collaborator

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.

@ldennington
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet