Skip to content

Conversation

@dimodi
Copy link
Contributor

@dimodi dimodi commented Feb 13, 2025

No description provided.

@dimodi dimodi added the merge-to-production Use this label to get a comment to choose whether to merge the PR to production label Feb 13, 2025
@dimodi dimodi requested review from a team as code owners February 13, 2025 13:23
@github-actions
Copy link
Contributor

Hello @dimodi,

Check the below option if you would like to automatically generate PR to production. The automation uses the branch for the cherry-pick, and then will delete the branch. Please, do not delete it manually.

  • create PR to production

@dimodi dimodi merged commit 9c17e5f into master Feb 13, 2025
1 check passed
@github-actions
Copy link
Contributor

Here you are the link to your PR to production: 2767

@github-actions github-actions bot deleted the license-key-note branch February 13, 2025 13:25
Copy link
Contributor

@ikoevska ikoevska left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed.

#### Can I use the same license key in multiple builds?

You can use your personal license key in multiple pipelines, builds, and environments. However, each individual developer must use their own unique personal license key.
You can use one license key in multiple pipelines, builds, and environments. However, each individual developer must use their own unique personal license key in their development environment.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in their respective development environment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge-to-production Use this label to get a comment to choose whether to merge the PR to production

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants