libgit2sharp | Git + NET = ❤ | DevOps library

What about something like

I was able to clone git repository by using the command:

How can I use GitHub PAT token for this Push?

Set that as your password to the credentials provider. A PAT is a password.

And if you've used your actual password in your question, please change it immediately.

LibGit2Sharp is a wrapper around libgit2, which is a C library that reimplements Git functionality. It's an independent library and doesn't use Git under the hood.

However, there are ways to use libgit2 to get information from the remote. Since I was unable to quickly find a web page with documentation for LibGit2Sharp, I'll show you the libgit2 documentation, and let you figure out what that looks like in .NET.

When you push with libgit2, you can specify a set of callbacks that the library can provide when certain events occur. This can be used to provide progress or other status information. The struct documentation indicates a member called sideband_progress, which is the callback for textual output that the remote side sends. In a normal git push invocation, that's the lines beginning with remote:.

Any time the remote side sends a complete line, that callback will be invoked and you'll get that output. Do note that often the output contains a carriage return to overwrite the previous entry and that the callback may be invoked a significant number of times, which may impact how you wish to store and process the output.

Now, having said that, the ideal way to get your data is by using the error code from the library, since that's going to be the easiest and most reliable way to get data. Parsing error messages is tricky; if you're talking to an arbitrary Git server, it's not guaranteed that it will use the same error messages as Git does, or even that any output it produces will be in English. Sometimes, though, you can't avoid it, so if that's the case, you now know how to do it.

Is there any way that I can do multiple operations in a single commit (either using the GitHub API or something else)?

There is the underlying Git Data API that can be used to build up a commit from scratch:

• files are uploaded as blobs using the API
• trees are used to indicate what the repository state should be (update paths to point to the new blobs)
• then create a new commit using the new root tree and additional metadata
• if you can, then update the reference (i.e. the branch) to point to this new commit

Is this a bug in dev.azure.com's way of doing GIT? Why have a "username" at all if it > > gets ignored anyway?

Nope, this is the expected action since you are using Git Credential Manager (GCM) to generate the password.

In fact, it is not an officially password. What it generated is a Personal access token after you click the button Generate Git Credentials, and its scope only to Repos(Read&Write).

At this time, go Security(https://dev.azure.com/{orgname}/_usersSettings/tokens) page, you will see there has one token be added which Token name is like git: https://dev.azure.com/{orgname} on {machine platform}.

For Personal access token, I'm sure you'd known that the PAT token are tied to a single user account when it generated. In another word, you doon't need input the username additionally while using PAT as authorize method. That's why the username get ignored anyway.

You can also check this doc to get How the Git Credential Managers works

Is this something I need to worry about?

Just treat it as password to keep secret will not cause too much issue.

Most of time, you don't need worry it. Because this token will expired very soon, will not longer than 1 day.

Also, as I mentioned above, the scope of this token are only to Repos with Read&Write permission. Even if someone accidentally gets this token, they can not make operation outside the Repos.

Ok so the solution to this problem consisted of two parts. Firstly, as colinD already suggested in his comment I had to go and change the configuration. Which I did. But it still didn't work for me. The reason was that the last time I committed and pushed my .sql files it had already replaced all line endings with LF in the remote repository. So I removed all the SQL files, commmitted and pushed the removal, re-added them, committed and pushed the re-added sql files, and then it worked.

As suggested by @EdwardThomson in his comment I then reverted back to the default settings and I added a .gitignore file instead. In the .gitignore file - at the same level as the .git folder in Windows - I added

Try and use a complete refsepc when pushing

The format of a parameter is an optional plus +, followed by the source object , followed by a colon :, followed by the destination ref .

In your case:

There is no need to "log out" in any way, shape or form. The remote repository remains inaccessible without credentials, even if the user installs GIT or TortoiseGit or some such. So I worried for no good reason.