Skip to content
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

Docker documentation (v6) #3858

Merged
merged 4 commits into from
Dec 31, 2023

Add documentation for Docker usage

1ee1193
Select commit
Loading
Failed to load commit list.
Merged

Docker documentation (v6) #3858

Add documentation for Docker usage
1ee1193
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Dec 31, 2023 in 3s

1 rule matches

⚠️ The pull request has been merged by @arturcic

✅ Rule: Thank contributor (comment)

  • -author~=^dependabot(|-preview)\[bot\]$
  • merged

💖  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: Automatic approve on dependabot PR (review)

  • author~=^dependabot(|-preview)\[bot\]$

Rule: Automatic merge on dependabot PR after success CI (merge)

  • author~=^dependabot(|-preview)\[bot\]$
  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • #commits-behind=0
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • -mergify-configuration-changed [📌 merge -> allow_merging_configuration_change setting requirement]
  • check-success=DotNet Format
  • check-success=Release
  • repository-full-name=GitTools/GitVersion
  • any of: [🛡 GitHub branch protection]
    • check-success=CodeQL
    • check-neutral=CodeQL
    • check-skipped=CodeQL
  • any of: [🛡 GitHub branch protection]
    • check-success=Build & Package / macos-latest
    • check-neutral=Build & Package / macos-latest
    • check-skipped=Build & Package / macos-latest
  • any of: [🛡 GitHub branch protection]
    • check-success=Build & Package / windows-latest
    • check-neutral=Build & Package / windows-latest
    • check-skipped=Build & Package / windows-latest
  • any of: [🛡 GitHub branch protection]
    • check-success=Build & Package / ubuntu-latest
    • check-neutral=Build & Package / ubuntu-latest
    • check-skipped=Build & Package / ubuntu-latest
  • any of: [🛡 GitHub branch protection]
    • check-success=DotNet Format
    • check-neutral=DotNet Format
    • check-skipped=DotNet Format
  • any of: [🛡 GitHub branch protection]
    • check-success=Test / macos-latest - net6.0
    • check-neutral=Test / macos-latest - net6.0
    • check-skipped=Test / macos-latest - net6.0
  • any of: [🛡 GitHub branch protection]
    • check-success=Test / macos-latest - net7.0
    • check-neutral=Test / macos-latest - net7.0
    • check-skipped=Test / macos-latest - net7.0
  • any of: [🛡 GitHub branch protection]
    • check-success=Test / ubuntu-latest - net6.0
    • check-neutral=Test / ubuntu-latest - net6.0
    • check-skipped=Test / ubuntu-latest - net6.0
  • any of: [🛡 GitHub branch protection]
    • check-success=Test / ubuntu-latest - net7.0
    • check-neutral=Test / ubuntu-latest - net7.0
    • check-skipped=Test / ubuntu-latest - net7.0
  • any of: [🛡 GitHub branch protection]
    • check-success=Test / windows-latest - net6.0
    • check-neutral=Test / windows-latest - net6.0
    • check-skipped=Test / windows-latest - net6.0
  • any of: [🛡 GitHub branch protection]
    • check-success=Test / windows-latest - net7.0
    • check-neutral=Test / windows-latest - net7.0
    • check-skipped=Test / windows-latest - net7.0
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