mateimicu / auto-tag Goto Github PK

Upgrade the project to use pipenv files.

There is a lot of duplication in tests
some e2e tests validate the same thing unit tests.

Refactor the tests and maybe rewrite some of them as BDD tests https://github.com/pytest-dev/pytest-bdd

Currently, the docs are quite messy (long output etc). We should structure them better and ad more examples on how to get started.

Pls,

list required packages to install auto-tag. It's boring to search in program code for required packages.

Or you add this to your package. ;o)

SemVer specifies the fact that you can add a suffix to the tag, for example, 2.0.33-develop a CLI option to append a prefix would help in supporting this kind of tagging strategy.

If the project is run in a pipeline then two processes may try to push the same tag, this will fail one pipeline ? can we handle this in the project in a way like a retry policy that will fetch new commits or this should be done outside

In order to avoid problems with dependencies run the pipeline using a corn

create structured documentation and publish it in gh-pages os something similar (readthedocs)

when you are deep in the structure of a repository you should try to go up and find .git

Investigate if there are any benefits

Is your feature request related to a problem? Please describe.
I want to change the prefix from v to rc

Describe the solution you'd like
A new CLI flag to include any prefix.

Describe alternatives you've considered
Duping the tag in a file and changing it manually.

https://github.com/CultureHQ/github-actions-badge

We have a few possibilities when looking for the last tag:

• last tag on a specific branch
• the biggest tag on this branch
• the biggest tag on from all of them (regardless of branch)

Currently, we implement the last one but if we want to use this tool on multiple branches then one of the first two options makes sense.