We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
some types require a unique name to work. for assets we already append (n) behind the name to automatically fix that if duplicates are wanted.
to enable us to deploy in parallel to an existing prod deployment, we shall need this also for:
The text was updated successfully, but these errors were encountered:
#1825: add auto-renaming to avoid duplicate-name error for automation…
bc22c5e
…, query and senderProfile
#1825: ensure validation rules do not block fixKeys
b9949a4
#1825: fix tests
1698982
Closed by #1827.
Sorry, something went wrong.
JoernBerkefeld
Successfully merging a pull request may close this issue.
some types require a unique name to work. for assets we already append (n) behind the name to automatically fix that if duplicates are wanted.
to enable us to deploy in parallel to an existing prod deployment, we shall need this also for:
The text was updated successfully, but these errors were encountered: