Update DISTOUT variable in build.sh to use RUNTIME variable instead of
hard-coding osx-x64.

macos build: use runtime instead of osx-x64

Deleted instruction concerning 'Expire access tokens' option when setting up OAuth app.

Delete outdated instruction for GitLab Support

Update release workflows to consume new autorotated SSL certificate. There
are two main parts:

1. Add the "SendX5c" : "true" key value pair to the contents of our ESRP
Auth Json file. This allows us to use the new auto-rotating certificate
without having to upload/manage it from our App Registration.i

2. Remove the AZURE_AAD_ID_SSL secret/environment variable. The new
certificate was generated with our main AZURE_AAD_ID app registration, so
this extra ID is no longer needed.

release: consume auto-rotated SSL certificate

Bumps [Newtonsoft.Json](https://github.com/JamesNK/Newtonsoft.Json) from 12.0.3 to 13.0.1.
- [Release notes](https://github.com/JamesNK/Newtonsoft.Json/releases)
- [Commits](JamesNK/Newtonsoft.Json@12.0.3...13.0.1)

---
updated-dependencies:
- dependency-name: Newtonsoft.Json
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>

Also adjusts the entire workflow to only run if a PR or push contains changes to a markdown file

Add broken link checking Action

The macos-10.15 image for CI builds is deprecated on GitHub Actions. We
should update this to a supported image.

Given we are actually running our release builds on macos-latest, we
should probably be running CI on the same image too!

Do not wait for the Git process to exit until we start reading from
the stdout stream, to prevent a deadlock. This is what we do in the
product code too.

Reorder Git config list process exit wait in diagnose command

Bumps [DavidAnson/markdownlint-cli2-action](https://github.com/DavidAnson/markdownlint-cli2-action) from 5.1.0 to 6.
- [Release notes](https://github.com/DavidAnson/markdownlint-cli2-action/releases)
- [Commits](DavidAnson/markdownlint-cli2-action@744f913...d199b6e)

---
updated-dependencies:
- dependency-name: DavidAnson/markdownlint-cli2-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>

…c/shared/Core/Newtonsoft.Json-13.0.1

build(deps): bump Newtonsoft.Json from 12.0.3 to 13.0.1 in /src/shared/Core

…ctions/DavidAnson/markdownlint-cli2-action-6

build(deps): bump DavidAnson/markdownlint-cli2-action from 5.1.0 to 6

Bumps [lycheeverse/lychee-action](https://github.com/lycheeverse/lychee-action) from 1.5.0 to 1.5.1.
- [Release notes](https://github.com/lycheeverse/lychee-action/releases)
- [Commits](lycheeverse/lychee-action@76ab977...4a5af7c)

---
updated-dependencies:
- dependency-name: lycheeverse/lychee-action
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

…ctions/lycheeverse/lychee-action-1.5.1

build(deps): bump lycheeverse/lychee-action from 1.5.0 to 1.5.1

The previous Azure resource architecture separated GCM and Microsoft Git
resources into different Resource Groups. This led to redundancy - we were
storing all our secrets, certificates, etc. in two places. These updates
reflect the consolidation of these resources into the new esrp Resource
Group.

release: update Azure storage resource names

Bumps [mjcheetham/update-homebrew](https://github.com/mjcheetham/update-homebrew) from 1.1 to 1.2.
- [Release notes](https://github.com/mjcheetham/update-homebrew/releases)
- [Commits](mjcheetham/update-homebrew@v1.1...v1.2)

---
updated-dependencies:
- dependency-name: mjcheetham/update-homebrew
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

…ctions/mjcheetham/update-homebrew-1.2

build(deps): bump mjcheetham/update-homebrew from 1.1 to 1.2

Update release asset regex to specify runtime and version groups so that
update-homebrew task can correctly detect version. Additionally, remove
alwaysUsePullRequest parameter so that Homebrew releases become automatic.

macos arm64: Homebrew updates

Add basic installer validation to release pipeline for Windows,
macOS (x64 only), and Linux (Debian package only). Validation runs the
installers/any necessary setup and checks that the installed version
matches the expected version.

release: add installer validation

The dotnet team recently added support for installing natively from Jammy feeds on
Ubuntu 22.04:

dotnet/core#7699

This unfortunately created problems with our current install from source
script, as it caused conflicts with
the packages.microsoft.com feed we use for Debian/Ubuntu.

This change modifies the Debian/Ubuntu dotnet install process to install from
Jammy feeds for users on Ubuntu 22.04 and greater while continuing to use
the packages.microsoft.com feed for Debian and older Ubuntu versions.

Update comments in the install from source script so that:

1. Sentences begin with capital letters.
2. Sentences end with punctuation.
3. Comments are within 80 characters per line.

Add a new workflow to create issues that will notify GCM users and
contributors of when maintainers are away and the repo is not being
actively monitored. This workflow is controlled by a `workflow_dispatch`
trigger that requires both a start date and end date for maintainer
absence before running.

workflows: auto-generate maintainer away issue

install from source: use native feeds for Ubuntu 22.04

Use --auth-mode login command to access ESRP Azure Storage Account instead
of AZURE_STORAGE_KEY. This allows us to reuse the git-fundamentals-esrp
service principal login credentials we're already using for other
resources and is a more secure mode of access than using the storage key.

release: access Azure Storage Account with login credentials

Switch to reference style links

Co-authored-by: Lessley Dennington <[email protected]>

Unify line length across docs

For some reason on macOS windows that are activated are not appearing on
top, and get lost behind other application windows. The platform
implementation on macOS is seemingly correctly calling the
`makeKeyAndOrderFront` native windowing API, but it's not being made
"key and front".

Setting the "topmost" flag true (and then false again) brings our
windows to the front, which is what we want.

Include the images resource across all the Avalonia UI applications.

Add config for several popular GitLab instances to docs

Add a generic credentials prompt view model and command for collecting
username/passwords.

Add an Avalonia-based UI prompt for the generic/basic credential prompt.

Add a WPF/Windows UI prompt for the generic/basic username and password
prompt.

Replace calls to the native system UI prompts with shelling out to the
generic helper UI.

Add generic username/password UI to all platforms

Bumps [actions/setup-dotnet](https://github.com/actions/setup-dotnet) from 2 to 3.0.0.
- [Release notes](https://github.com/actions/setup-dotnet/releases)
- [Commits](actions/setup-dotnet@v2...v3.0.0)

---
updated-dependencies:
- dependency-name: actions/setup-dotnet
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>

When we transitioned our release workflow to GitHub actions, we started
using Powershell's `Compress-Archive` cmdlet to zip our Windows binaries.
However, this unfortunately does not play nicely with `unzip` in WSL.
Since we're publishing the archives from an Ubuntu machine, switch to
creating the archives with the `zip` command in the default bash shell to
correct the issue.

release: fix Windows archives

…ctions/actions/setup-dotnet-3.0.0

build(deps): bump actions/setup-dotnet from 2 to 3.0.0

Bumps [actions/setup-dotnet](https://github.com/actions/setup-dotnet) from 3.0.0 to 3.0.1.
- [Release notes](https://github.com/actions/setup-dotnet/releases)
- [Commits](actions/setup-dotnet@v3.0.0...v3.0.1)

---
updated-dependencies:
- dependency-name: actions/setup-dotnet
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

Use the WriteDictionarySecrets() method to safely log the dictionary of data that will be written back to the calling Git process

When it is necessary to follow the processing in GCM during a call from Git the GCM_TRACE environment variable can be used to print trace information to standard error, however the ultimate output of GET commands would not be included in this trace information

This lack of visibility is especially problematic during multi-stage authentication such as OAuth, adding safe logging of the final output makes it possible to follow the GCM process in realtime from inputs to outputs during Git GET requests

…of Bitbucket DC's OAuth2 implementation

The BitbucketAuthentication and BitbucketHostProvider remain the single points of entry to processing authentication for all Bitbucket hosts.

Bitbucket DC and Bitbucket Cloud do not share common REST APIs or common OAuth2 implementations. The interface IBitbucketRestApi and abstract class BitbucketOAuth2Client effectively hide the differences in implementation from BitbucketAuthentication and BitbucketHostProvider

The interface IBitbucketRestApi and abstract class BitbucketOAuth2Client provide clear extension points to implement OAuth2 support for Bitbucket DC

New implementations of the interface IBitbucketRestApi and abstract class BitbucketOAuth2Client provide client code for interacting with the Bitbucket DC REST API and OAuth2 implementation. Extending the BitbucketRestApiRegistry and OAuth2ClientRegistry to provide these Bitbucket DC implementations when a DC host is detected means BitbucketAuthentication and BitbucketHostProvider remain agnostic about which form of Bitbcuket host they are interacting with

Prior to this feature users were limited to using Basic Auth or HTTP Access Tokens to interact securely with a Bitbucket DC instance. OAuth2 provides a better solution for SSO environments

…ket DC

Update docs/environment.md and docs/configuration.md to document the new configuration options for managing Bitbucket DC OAuth2 Client ID and Client Secrets

Update docs//bitbucket-development.md to document how to create a test Bitbucket DC environment and OAuth2 setup

Bumps [actions/checkout](https://github.com/actions/checkout) from 3 to 3.1.0.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v3...93ea575)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

Use a short link for the Linux install from source script.

Signed-off-by: Matthew John Cheetham <[email protected]>

The current URLs use an outdated source.

The rfc-editor.org site is stated to be the authoritative source, see aaragraph 3 on https://www.ietf.org/standards/rfcs/.

The redirection used at the existing URL cause the later versions of the link checker to fail for the instances in the documentation. However, instances in the source code comments have also been updated.

Fixes #863

Adds a brief section to the `docs/document.md` on how linting of documents is done.

…ctions/actions/setup-dotnet-3.0.1

build(deps): bump actions/setup-dotnet from 3.0.0 to 3.0.1

…stall-link

docs: use short link for Linux install src

Updates RFC links to authoritative URL

Replace githubusercontent images

Document how to lint documentation

…ucket-DC

Issue/573 OAuth2 support for Bitbucket DC

…ctions/actions/checkout-3.1.0

build(deps): bump actions/checkout from 3 to 3.1.0

Add a new `DotnetTool` project containing the needed files to publish GCM
as a cross-platform dotnet tool. Additionally, update GCM to use helper
dlls if exes are not found in the Application directory. At present, dlls
are only used in the dotnet tool scenario to minimize the package size and
to make it cross-platform compatible.

release: package gcm as dotnet tool

Change the name and author of the dotnet tool package from
GitCredentialManager.Cli to git-credential-manager. The reason for this
change is that we were able to transfer ownership of this package (which
was previously owned by JetBrains) to the git-credential-manager
organization on NuGet.org.  There should not be any customer impact
related to this change, as the GitCredentialManager.Cli package had yet
to be published.

dotnet tool: rename package

Bumps [actions/setup-dotnet](https://github.com/actions/setup-dotnet) from 3.0.1 to 3.0.2.
- [Release notes](https://github.com/actions/setup-dotnet/releases)
- [Commits](actions/setup-dotnet@v3.0.1...v3.0.2)

---
updated-dependencies:
- dependency-name: actions/setup-dotnet
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

We forget to include the core UI helper (WPF) in the Windows installer
manifest.. add it!

Rename the main entry executable from git-credential-manager-core(.exe)
to simply git-credential-manager(.exe), now that the older GCM4W has
been removed from the Git for Windows project as an option (and the GCMC
project has been renamed).

We do not rename the Debian package ID, nor the Homebrew Cask name yet
as this will require more thought for migration.

Include git-credential-manager-ui.exe in installer

…ctions/actions/setup-dotnet-3.0.2

build(deps): bump actions/setup-dotnet from 3.0.1 to 3.0.2

Explicitly pass the version and build configuration to the dotnet tool
packaging script. Also revert to a default Debug config for local
builds; this is consistent with all other artifacts in the build for dev
(macOS pkg, Windows installers, deb, etc)

Add the GCM icon to the NuGet package used for the dotnet tool.
The image is copied to the root of the package under a new `images`
directory (/images). The tool payload continues to be copied under the
required `/tool/net6.0/any` directory.

Modify the pack-tool.sh script to keep all build output under the /out
directory of the repository (which is in .gitignore). Output from
running pack-tool.sh now looks like this:

.
└── out
    └── shared
        └── DotnetTool
            └── nupkg
                └── Debug
                    ├── git-credential-manager.$VERSION.nupkg
                    ├── images       # icon
                    ├── payload      # dotnet publish output
                    └── payload.sym  # pdbs

The contents of the NuGet package looks like this:

.
├── [Content_Types].xml
├── _rels
├── git-credential-manager.nuspec
├── images
│   └── icon.png          # copied from the output images/ dir
├── package
│   └── services
│       └── metadata/...
└── tools
    └── net6.0
        └── any/...       # copied from the output payload/ dir

Fix a bug that was introduced in an earlier PR to build the Core UI
helper (WPF) for Windows. We don't need to specify the TFM or RID for
these projects.

We missed the core UI helper from the dotnet tool package - include it!

Add icon to dotnet tool NuGet package

This required fixing some newly found lint issues.

Additionally some issues are in files (workflow templates) that are structured in such a way that do not easily allow correction, so I have adjusted the linter configuration to ignore these files for now. They could instead be corrected in a later commit.

…vices.

Create symlinks and shim/copy-executables for the original exec
"git-credential-manager-core(.exe)" name for consumers who have not
updated to the new name.

We detect if the consumer is launching us via the "-core" symlink or
executable shim by consulting the platform-native APIs to get the
original "argv[0]". All of the .NET APIs sadly don't give us the real
"argv[0]", so we need to use native APIs...

If we detect use of the old name, print a warning that the user should
update their configuration, and a help link for more information.

Add documentation with information about the GCM.exe rename, and how to
fix-up any configuration after the change.

The aka.ms/gcm/rename shortlink points to this document.