Split out the IGit and IGitConfiguration interfaces and extension
methods in to their own files.

Add ability to locate executables on the current PATH by shelling out to
`which` on UNIX platforms, and `where.exe` on Windows.

Implement IGit and IGitConfiguration components using the Git CLI
executable, rather than libgit2.

Update the use of the Git configuration components in the configuration
service and configurable components; used to set up a system during
install.

Add an implementation of the IFileSystem component for Linux
distributions. We just simply assume that all file systems are
case-sensitive at the moment.

Also introduce a (empty) PosixFileSystem class shared between macOS and
Linux.

Implement a stub ISystemPrompts component that just throws.
The component is currently not used on any platform that's not Windows
anyway so this won't be hit.

Implement a credential store for Linux platforms that use the libsecret
Secret Service API.

Update the Nerdbank.GitVersioning package to the latest to fix a bug
where the package would fail to execute due to libgit2 dependency
issues.

Extend the PR and CI build to produce a tarball of binaries for Linux
x86_64 platforms; building on Ubuntu 18.04 LTS.

The release build does not publish anything currently as we need to get
signing working.

Rewrite the libsecret and glib interop code for the Linux
ICredentialStore implementation to be more thorough.

Introduce a credential store for Linux that passes through to a backing
store that is selected based on user preference and session features.

Currently this is a stub that just uses LibsecretCollection (which only
works in a GUI environment).

Rename the LibsecretCollection type to SecretService API to more
accurately reflect the API we're using.

Ensure the PR build is triggered on PRs into master or release.
Also now that we're making real releases of GCM Core on GitHub and not
just pre-releases, move to the simpler syntax/API calls for the Action
that creates and updated the Homebrew cask on release publish.

Fix workflows and builds

On release, automatically update the Homebrew Cask in the microsoft/git
Tap.

Automatically update Homebrew Cask on release

Make OAuth the default authentication mode.

Move the OAuth/login with browser option to the top of the Windows
GitHub login dialog when both user/pass and OAuth options are available.

Replace the "login using browser" link with a button on the Windows
GitHub login dialog.

Make OAuth the default authentication mechanism for GitHub provider

… the versioning task works

Starting the creation of a Github Actions CI workflow, specifically including Linux.

Add initial Ubuntu & Secret Service support

Signed-off-by: Derrick Stolee <dstolee@microsoft.com>

For some situations, the key-value pairs we split from the response of
'git config' do not have two elements. Be careful to check the length
before returning the value. If the length is not two, then this is an
invalid key-value pair so skip that entry.

Signed-off-by: Derrick Stolee <dstolee@microsoft.com>

1. When we re-set the configuration, we pass an empty value to clear the
existing values. However, that only works if we quote around the empty
value. Otherwise, Git does not "see" a value argument.

2. If there is no configuration for a given key, the exit codes for 'git
config' change. See the documentation [1] for full details. For now, be
careful about exit codes 1 and 5, when appropriate.

[1] https://git-scm.com/docs/git-config

Signed-off-by: Derrick Stolee <dstolee@microsoft.com>

… configure' with empty config

Resolves #161. The failures were due to subtleties when working without any `credential.helper` values in any level of config. This is typical for a fresh install on a Linux machine, but never happens with Git for Windows. Git on macOS might also come pre-loaded with this config.

The build configuration "Release" only builds the managed portions of
GCM Core. However, on macOS and Windows we have UI bits that are native
to each platform. Update the --configuration build option to include
these native bits by casing on the "os" variable in the matrix build.

Signed-off-by: Derrick Stolee <dstolee@microsoft.com>

…nd we need that output.

CI: update configuration to build native bits

Add a Linux .deb installer CI workflow

Update the ICredentialStore and ICredential API to allow for smarter
searching of stored credentials.

The new API exposes filtering by "service name" and "account"
separately. Service name will typically be the URL the credential is
stored against, and the account will be the username associated with the
credential.

Update the macOS Keychain component implementation to match the new
ICredentialStore interface. We now use the `SecItemCopyMatching` to
perform a general query for items, and return a specialised credential
object including all relevant attributes.

Update the Windows Credential Manager component to implement the new
ICredentialStore interface, including credential enumeration and
matching by account/user as well as 'service name' (target).

Recover the correct service name from the target name.

Since the target name may contain a userinfo component (for example
https://alice_domain.com@example.com/path), and the only place we store
the service name is in the target name, we need to strip out any
userinfo component.

We do this by looking for the "://" and the first '@' character before
the first '/', which act as the start and end of the userinfo component.

Update the SecretServiceCollection credential store (backed by
libsecret) to match the new ICredentialStore interface and access
model.

Update the remote URI generation from the program InputArguments to
support port numbers, and special characters in usernames.

Update the HostProvider base class to use the new 'service name'
abstraction rather than the simple 'unique credential key' one.

With this model we can better issue credential storage queries where the
username may not be specified explicitly in a get request (often the
case as the username is not always included in the remote URL for many
services).

Update the generic host provider to support the new credential storage
model and HostProvider base class APIs.

Update the Basic authentication component to match the new ICredential
interface.

Update the BitBucket provider to support and implement the new
credential storage/recall model and APIs.

Update the GitHub provider to implement and follow the new credential
storage/recall/matching model and ICredentialStore APIs.

Update the Azure Repos provider to support the new credential storage
API/model, as well as support remote URLs with explicit port numbers.

Now that we support multiple user accounts for each host/service/remote,
we have hit an interesting issue with Azure Repos.

With the introduction of the dev.azure.com-style URLs for Azure Repos
there was an unfortunate hack or workaround invented to add the AzDevOps org name
to the userinfo part of the remote URL, for example: org@dev.azure.com/org/blah.

Since GCM for Windows (and older versions of GCM Core that initially followed
the same model) always uses the value "PersonalAccessToken" for the username field
when storing credentials it was free to ignore the user part of the input.

The problem now is that since we support multiple user accounts, and will perform
an exact match against the credential (with user) if a username is specified in
the remote URL, we never find the credential we now store (we now always store
with the actual, real users' UPN).

To workaround this workaround (yuck) we ignore the username IF AND ONLY IF the
host is dev.azure.com, and return the first matching dev.azure.com/org
credential. The upshot of this is that dev.azure.com-style URLs do NOT
support multiple users OR full paths, however vs.com-style URLs will.

Add support for customising the namespace/prefix used to store
credentials in the OS credential store.

By default we use "git:{service}". Users can use GCM_NAMESPACE or
credential.namespace to set this to something different.

These configuration options are the same as in GCM for Windows to help
with migration.

Update the GCM Core Host Provider spec document and architecture
document to reflect the changes made to the abstract HostProvider
class; replacing GetCredentialKey with GetServiceName.

Fix a bug in the WindowsEnvironment implementation of the
LocateExectuable method. On .NET Core the UseShellExecute property of
ProcessStartInfo defaults to false, whereas on .NET Framework (the
runtime that we target on Windows) defaults to true. You must set this
to false if you want to redirect standard streams (which we want to do).

The .NET Framework-targeting build on Windows was throwing an exception
here(!)

Revamp credential storage system to allow for smarter searching

Now that we have the GCM OAuth application in the allow-list for GitHub
apps, we no longer need to offer username/password authentication for
github.com!

Fix a typo in a constant variable indicating the available
authentication modes for github.com.

Remove username/password authentication for github.com

Change how we construct the existing credential stores by simply new-ing
them up, rather than calling a static `Open` method.

Add a plaintext credential store option for Linux. Credentials are
stored in plaintext files, by default in ~/.gcm/store, but configurable
by settings/environment variables.

Users can select between the Secret Service API and plaintext-based
credential storage using the GCM_CREDENTIAL_STORE setting.

Refactor the PlatformFact attribute to support a flags enum, such that
compound platforms can be specified (e.g., Posix = Linux | Mac).

Add a `pass` compatible credential store that uses GPG to store
encrypted credentials in files on disk. Defaults to the default `pass`
password store, but can be overriden using standard `pass` envars.

Add a document outlining the different credential stores available on
Linux.

Extract the Linux Credential Store option constant values.

Add a variety of credential stores on Linux

Add Linux Azure Pipelines release