Allow for "dynamic" branches when specifying Config branch in trigger in the pipeline config

It would be very useful for testing CI config changes if we could specify a dynamic config branch, more specifically have the branch name match the event source’s branch.

For example, I have a repository called my-repo
I have a pipeline configured with the following:
Config source: central-config-repo
Config filepath: shared-configs/config.yml
Checkout source: my-repo
Trigger on…
Event: ”run-ci” label added to PR
Event source: my-repo
Config branch: * ←This is the request, I would like to be able to put in a special character or word that automatically matches the branch from my-repo

So if I check out a branch in my-repo called testing-something-that-needs-a-ci-config-change and push a change to a PR, I would like the pipeline trigger to fill in testing-something-that-needs-a-ci-config-change in the Config branch.

What this accomplishes is it allows me to more easily test changes to a CI config in my central-config-repo

Can such a feature be added?