Skip to content

fix: set propagateTags to null if unset #736

New issue

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

Merged
merged 1 commit into from
Mar 7, 2025

fix: set propagateTags to null if unset

831d9c5
Select commit
Loading
Failed to load commit list.
Merged

fix: set propagateTags to null if unset #736

fix: set propagateTags to null if unset
831d9c5
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Mar 7, 2025 in 0s

1 potential rule

⚠️ The pull request has been merged by @dani-chmb

Rule: Automatically merge on CI success and review approval (queue)

  • -closed
  • -closed [📌 queue requirement]
  • -merged
  • approved-reviews-by=@aws-actions/aws-ecs-devx
  • #approved-reviews-by>=1
  • -approved-reviews-by~=author
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • -title~=(WIP|wip)
  • author!=dependabot[bot]
  • base~=master|integ-tests
  • label!=work-in-progress
  • status-success=Analyze (javascript)
  • status-success=Run Unit Tests
  • status-success=Semantic Pull Request
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-success = Analyze (javascript)
        • check-neutral = Analyze (javascript)
        • check-skipped = Analyze (javascript)
      • any of: [🛡 GitHub branch protection]
        • check-success = Package distribution file
        • check-neutral = Package distribution file
        • check-skipped = Package distribution file
      • any of: [🛡 GitHub branch protection]
        • check-success = Semantic Pull Request
        • check-neutral = Semantic Pull Request
        • check-skipped = Semantic Pull Request

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


2 not applicable rules

Rule: Automatically approve and merge Dependabot PRs (queue)

  • -closed
  • -closed [📌 queue requirement]
  • -merged
  • author=dependabot[bot]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • -label~=(blocked|do-not-merge)
  • -title~=(WIP|wip)
  • base=master
  • status-success=Analyze (javascript)
  • status-success=Run Unit Tests
  • status-success=Semantic Pull Request
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-success = Analyze (javascript)
        • check-neutral = Analyze (javascript)
        • check-skipped = Analyze (javascript)
      • any of: [🛡 GitHub branch protection]
        • check-success = Package distribution file
        • check-neutral = Package distribution file
        • check-skipped = Package distribution file
      • any of: [🛡 GitHub branch protection]
        • check-success = Semantic Pull Request
        • check-neutral = Semantic Pull Request
        • check-skipped = Semantic Pull Request

Rule: Automatically approve and merge Dependabot PRs (review)

  • -closed
  • -merged
  • author=dependabot[bot]
  • -label~=(blocked|do-not-merge)
  • -title~=(WIP|wip)
  • base=master
  • status-success=Analyze (javascript)
  • status-success=Run Unit Tests
  • status-success=Semantic Pull Request
Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com