git vs fabric item naming

[NL27496]

There are workspace item names that are allowed in fabric, but cause issues in GIT. This happens after merging changes between two git branches. A referencing pipeline in the updated workspace cannot he run. The name db-1 results in an error. The name db_2 is allowed.

I have two workspaces. ws1 and ws2. Both are connected to git. wis 1 is connected to a git branch named b-dev , ws2 is connected to git branch called b-test.

I have a data pipeline called dp1, that is in ws1. This has a copy activity that transfers data from a Sqlserver in azure to one lake sqldb (in ws1 and ws2).

This runs without errors in ws1.

If I now do a git-pr to merge the git branche b-dev into b-test, with no merge conflicts I expect to be able to run dp1 in ws2.

However this gives an error because of invalid references.

Some years ago this was a known issue.

Has this been fixed?. Is this currently a supported scenario?

Can i use a git PR in combination with fabric, in i only use a _ (underscore) and a-z,  in the name?

I rather not use deplomnet pipelines in git as they don't have enough functionality. Should I use fabric deployment pipelines instead of a PR? Or is there another way to get my sql-dababase named db-3 (with hyphen) from ws 1 to ws2 and have valid pipelines afterwoulds ?

[NL27496]

I suppose this situation was a remainder of recent service outages. I will retest next week.