[QUESTION] Extend Pre Release Policies?

[fcl-9]

Hi,

First would like to congratulate you on building keel.sh its an amazing tool.

I am trying to use Keel in a project however I am using GitVersion in order to have automatic versioning,
this effectively means that my images pushed into the container registry have tags with metada such as:

For Features: 1.0.0-branch_name.X
For Dev: 1.0.0-dev.X
For Release Stabilisation/Pre Release: 1.0.0-revision.X

Where X increases for every commit in a branch, and every commit generates a new image that can be deployed and tested.
These tags metadata (-branch_name.X, -dev.X, -revision.X) will only be removed once we merge a stable release branch into the main which will generate a 1.0.0 image.

After reading the documentation on pre-release policies seems that the default keel policies won't be able to track these types of tags as X keeps being incremented. I have been wondering if there would be any way for us to extend/create custom policies to be able to tell keel trach images with non-static metadata?

I tried to add a question label to this issue but could not select it.
Thanks in advance