Use restorecon for usbguard config-file SELinux context - #652

Rule: approve dependabot pull requests (review)

• author=dependabot[bot]

Rule: merge dependabot pull requests (merge)

• -closed [📌 merge requirement]
• author=dependabot[bot]
• #approved-reviews-by>=1
• -conflict [📌 merge requirement]
• -draft [📌 merge requirement]
• github-review-approved [🛡 GitHub branch protection]
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = @mergify/Configuration changed
  • check-success = @mergify/Configuration has been deleted
• any of: [🛡 GitHub branch protection]
  • check-success = test (8, ash-linux.iavm, ./tests/pillar/test-linux-main) / test
  • check-neutral = test (8, ash-linux.iavm, ./tests/pillar/test-linux-main) / test
  • check-skipped = test (8, ash-linux.iavm, ./tests/pillar/test-linux-main) / test
• any of: [🛡 GitHub branch protection]
  • check-success = test (8, ash-linux.stig, ./tests/pillar/test-linux-main) / test
  • check-neutral = test (8, ash-linux.stig, ./tests/pillar/test-linux-main) / test
  • check-skipped = test (8, ash-linux.stig, ./tests/pillar/test-linux-main) / test
• any of: [🛡 GitHub branch protection]
  • check-success = test (8, ash-linux.vendor, ./tests/pillar/test-linux-main) / test
  • check-neutral = test (8, ash-linux.vendor, ./tests/pillar/test-linux-main) / test
  • check-skipped = test (8, ash-linux.vendor, ./tests/pillar/test-linux-main) / test
• any of: [🛡 GitHub branch protection]
  • check-success = lint / actionlint
  • check-neutral = lint / actionlint
  • check-skipped = lint / actionlint
• any of: [🛡 GitHub branch protection]
  • check-success = lint / tardigradelint
  • check-neutral = lint / tardigradelint
  • check-skipped = lint / tardigradelint
• any of: [🛡 GitHub branch protection]
  • check-success = test (9, ash-linux.iavm, ./tests/pillar/test-linux-main) / test
  • check-neutral = test (9, ash-linux.iavm, ./tests/pillar/test-linux-main) / test
  • check-skipped = test (9, ash-linux.iavm, ./tests/pillar/test-linux-main) / test
• any of: [🛡 GitHub branch protection]
  • check-success = test (9, ash-linux.stig, ./tests/pillar/test-linux-main) / test
  • check-neutral = test (9, ash-linux.stig, ./tests/pillar/test-linux-main) / test
  • check-skipped = test (9, ash-linux.stig, ./tests/pillar/test-linux-main) / test
• any of: [🛡 GitHub branch protection]
  • check-success = test (9, ash-linux.vendor, ./tests/pillar/test-linux-main) / test
  • check-neutral = test (9, ash-linux.vendor, ./tests/pillar/test-linux-main) / test
  • check-skipped = test (9, ash-linux.vendor, ./tests/pillar/test-linux-main) / test

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