Ervin Hegedus

> You can get the version by looking at the latest tag, e.g., `git describe --tags`, that will give you something like `v4.2.0-75-g6a3df157` if the current commit is ahead of...

> `git describe` is not the same as `git describe --tags`. You need `--tags` because we don't use annotated tags. Ah, this makes sense - thanks. This works for me...

Proposed solution: * `crs-setup.conf.example` contains rule [900990](https://github.com/coreruleset/coreruleset/blob/main/crs-setup.conf.example#L810-L818) * that rule's [tag](https://github.com/coreruleset/coreruleset/blob/main/crs-setup.conf.example#L816) would be the reference for version `tag` * and that rule's [ver](https://github.com/coreruleset/coreruleset/blob/main/crs-setup.conf.example#L817) would be the reference for `ver` action...

``` $ git describe --tags v4.5.0-5-g25afc1e8 $ tail -n 3 crs-setup.conf.example tag:'OWASP_CRS',\ ver:'OWASP_CRS/4.6.0-dev',\ setvar:tx.crs_setup_version=460" ``` so, what is the correct version? `v4.5.0-5` or `4.6.0-dev`? The other question: is there any...

Is `git` command available inside of GH workflow?

> `4.6.0-dev`. `-5` is the number of commits since the `v4.5.0` tag. The other problem is that to get the correct tag, everyone needs to fetch them explicitly. I mean...

I have a downloaded repository. It's very "old", I usually work there. Here is what I saw today: ``` $ git describe --tags v4.2.0-255-g25afc1e8 $ git fetch --tags upstream remote:...

#3788 solves this, we can close the issue.

Hi @racer1950, thank you for your report. First, please note, that the triggered rule is not just the `949110` - indeed, this is the only rule, which triggered because the...

Hi Robert, as I suggested above, **please do not make any exception** for rule 949110. It's highly recommended to keep it active. The other rules do not stop the process...