-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
Suppress 'v' prefix in tag #140
Comments
This is the lines that control this behaviour: sphinx-github-changelog/sphinx_github_changelog/changelog.py Lines 116 to 119 in 58db359
Do you want to make a PR ? |
Due to corporate policy I need to file paperwork for each open source project I wish to contribute code to. I've requested approval for sphinx-github-changelog but it will take some time. |
Wow, good luck with that :) If there's anything I can do to help, let me know :) (also, I really hope this only applies to contribution on your work time and not on your free time, otherwise that must feel invasive as hell :o ) |
I have a very similar approval needed for contributions on my own time, but there is less scrutiny and it gets approved a lot faster. But yes.
No, not at all. You requested that I do it, so I was just answering that question. |
It is a common practice to tag releases as
v1.2.3
for version1.2.3
.From semver.org:
I'm relying on this convention for a few reasons, like GitHub Actions automation with
and sometimes
When using this practice, the generated changelog contains headings like
v0.1.2: 0.1.2
If the tags omit the
v
prefix then the tag name is omitted from the heading but it is more challenging to write GitHub Action automations that match release tags.I would like the
v
to be disregarded when comparing the tags and release versions, so that the heading comes out as0.1.2
The text was updated successfully, but these errors were encountered: