gitdir | Download a single directory/folder from a GitHub repo | Download Utils library

I believe what you want is the first token from the output of git describe --tags.

The two commands serve different purposes.

git ls-remote lists the references on a remote repository, but does not make any promises about the ordering in which they are listed. Sure, the most recent one is typically last, but it's not necessarily the most relevant one, especially if that tag was on a branch that didn't get merged yet.

git describe, on the other hand, is trying to give you a concise description of HEAD (by default, or the commit you specify) with respect to the most recent tag reachable from there. If you use your tags only for stable commits, then that's probably going to be the tag you want. Then, once it found that tag, it tells you how many more commits are in HEAD, 606 of them in your example, then "g" (not sure why), then the sha1 of HEAD. This is meant to be a human-readable description of any commit, as in, "oh, you're 606 commits ahead of v2.31.1", but also an unambiguous description, since you get the sha1.

As for adding the --tags option to git describe, you need it if you have tags without annotations, e.g., if some where created using git tag   instead of git tag -a . The latter is preferable, since it allows the tagger to describe the contents of the tag, but you can't always count on everyone using it. So it's probably a good idea to add --tags to git describe.

If your repo only contains tags for stable releases, and those releases are not on a different release branch, and you never have hyphens in your tag names, then this would be the most recent stable release that's a parent of HEAD:

Thanks to @torek I'm find a solution in this question:

Store keychain credentials for multiple github accounts

I was trying use two github accounts with ssh keys, but in MAC needs keychain. So when a repository is cloned we need to do it via HTTPS including user and no vía SSH like this:

Let's find out!

The easiest way to find out what exactly was matched by a regex pattern in any version of PowerShell is by using Regex.Matches():

You are not the first to ask this question, see this feature-request from 2016

Relative paths seem to complicate things:

• when moving a worktree (note that a worktree can be inside or outside the parent repository)
• when moving the parent repository

So it seems this never got implemented...

The RASA_ENDPOINT_URL capability has to point to the base URL of your Rasa server - without the /webhooks/rest/webhook path. Botium will build up it's own full url endpoint path based on the RASA_MODE capability:

• NLU_INPUT => /model/parse is appended
• REST_INPUT => /webhooks/rest/webhook/ is appended

The short answer is no.

The .git file (when there is a .git file) must occupy the top level of the working tree, so if you have a .git file, the directory in which that .git file lives is the working tree. So there's no point in listing the working tree path: it's implied by the fact that you used that path to open the file named .git. This does of course mean that you have to remember the path you used to open the file named .git, which in some circumstances is a bit of a pain point, but that's why the answer is no.

I end up separating the git config files and git credentials as below. The below setting ables me to separate all repositories' credentials from that of under work/ directory.

(Didn't know that .git-credentials automatically handles it by appending the credentials in plain text.) Thanks.

1. ~/.gitconfig

Untracked files are files/directories on disk, which aren't tracked yet by git, and which aren't explicitly ignored either.

You can either tell git to ignore it, or remove that file/directory from disk :

Add a final /: