Feature/icm/834 fix ingress annotation conflict in icm web chart

[skiesewetter-intershop]

PR Type

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no API changes)
• Build-related changes
• CI-related changes
• Documentation content changes
• Application / infrastructure changes

What Is the Current Behavior?

Issue Number: Closes #834

What Is the New Behavior?

Does this PR Introduce a Breaking Change?

• Yes
• No

[github-actions]

Test Results

  1 files   33 suites   1s ⏱️
164 tests 164 ✅ 0 💤 0 ❌
165 runs  165 ✅ 0 💤 0 ❌

Results for commit ebc15ba.

[github-actions]

Test Results

7 tests   7 ✅  0s ⏱️
3 suites  0 💤
1 files    0 ❌

Results for commit ebc15ba.

♻️ This comment has been updated with latest results.

[DevDavido]

Target branch main instead of develop/icm @skiesewetter-intershop?

[tvalchev2]

Thank you for fixing the ingress annotation.

It is better if we don't define ingress specific annotations directly in the helmchart, since that binds us to nginx as ingress controller and this cannot be changed easily, if decided to go for another controller

The base branch was changed.

[skiesewetter-intershop]

Target branch main instead of develop/icm @skiesewetter-intershop?

Oh, like nearly always I selected to wrong branch. But why is no new build triggered if I change the target branch?

[DevDavido]

[...] But why is no new build triggered if I change the target branch?

Our current workflow triggers don't react on such edited activity type, but by default only on open, synchronize and reopened:
https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#pull_request