Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 17.94%. Comparing base (93239e0) to head (9decc77).

@@             Coverage Diff              @@
##               main   #12823      +/-   ##
============================================
- Coverage     17.95%   17.94%   -0.01%     
+ Complexity    16259    16256       -3     
============================================
  Files          5954     5954              
  Lines        534838   534838              
  Branches      65423    65423              
============================================
- Hits          96010    96000      -10     
- Misses       428053   428063      +10     
  Partials      10775    10775              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

refs #12164

@jbampton , would it be possible to run only if org/repo is apache/cloudstack and if branch in {main, 22, …} ?

@jbampton , would it be possible to run only if org/repo is apache/cloudstack and if branch in {main, 22, …} ?

From Google:

To run Dependabot only on the upstream repository and not on forks, you no longer need to manually disable it in every fork; Dependabot version updates are now disabled by default for all new forks created after November 7, 2022.
If you are dealing with forks created before that date, or if updates were previously enabled, you can manage them as follows:

1. Default Behaviour for Forks

• New Forks: When a repository with an existing dependabot.yml is forked, version updates are automatically disabled. The owner of the fork must explicitly click "Enable" in their repository's settings to start receiving updates.
• Existing/Old Forks: For forks created before the 2022 change, Dependabot may still be active if it was inherited from the upstream config.

2. How to Manually Disable on a Fork
   If Dependabot is active on a fork and you want it stopped, use one of these methods:

• Repository Settings: Go to Settings > Code security and analysis (or Advanced security) and click Disable next to "Dependabot version updates".
• Re-forking: Delete the existing fork and re-create it; the new fork will have Dependabot disabled by default.
• Delete Configuration: Some users remove the .github/dependabot.yml file from their fork's branch, though this can cause merge conflicts with the upstream repository later.