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.

Sign up for GitHub

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

Jump to bottom

Support tags where appropriate? #29

Open
lickel opened this issue Mar 20, 2023 · 1 comment
Open

Support tags where appropriate? #29

lickel opened this issue Mar 20, 2023 · 1 comment

Comments

@lickel
Copy link

lickel commented Mar 20, 2023

I had previously implemented this years ago in a fork of a prior incarnation of this project.

If you use git describe --exact-match you can access the current git tag as opposed to a SHA.
This aids in readability for some workflows.
@thomasrebele
Copy link

That would indeed be a nice-to-have feature. It seems that the option --all or --tags needs to be specified to make it work with all kinds of tags (c.f. https://stackoverflow.com/a/61182221).

~/zsh-git-prompt[:7f406e4 L|✔]$ git describe --exact-match      
fatal: no tag exactly matches '7f406e4d66ce7b286899ab18d6d482435d92fcb8'
~/zsh-git-prompt[:7f406e4 L|✔]$ git describe --exact-match --tags
v0.6

alewis001 pushed a commit to alewis001/zsh-git-prompt that referenced this issue Feb 13, 2024
@jonathanmdr
Removing typos in the README file to use copy button correctly (zsh-g…
cc8e2d1 
…it-prompt#29)

In the section of `brew` commands, when the copy button has been used, the character `$` is copied together with the brew command and It causes an error on the user terminal.

Removing the `$` character promotes the best experience for users.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lickel @thomasrebele