Skip to content

feat: add reliability score - #673

Open
avanibapna06 wants to merge 5 commits into
AditthyaSS:mainfrom
avanibapna06:feat/reliability-score
Open

feat: add reliability score#673
avanibapna06 wants to merge 5 commits into
AditthyaSS:mainfrom
avanibapna06:feat/reliability-score

Merge branch 'main' into feat/reliability-score

8cddfb6
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jul 28, 2026 in 2s

2 rules match and 11 potential rules

Rule: Thank contributor on merge (comment)

  • merged

Rule: Welcome first time contributor (comment)

  • #commits = 1
  • author != AditthyaSS

Rule: Auto merge when approved (merge)

  • #approved-reviews-by>=1
  • #commits-behind = 0 [🛡 GitHub repository ruleset rule Protect main]
  • -conflict [📌 merge requirement]
  • -closed [📌 merge requirement]
  • -draft [📌 merge requirement]
  • check-success=Summary
  • github-review-approved [🛡 GitHub repository ruleset rule Protect main]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [📌 merge requirement]
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections
  • any of: [🛡 GitHub repository ruleset rule Protect main]
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections
  • any of: [🛡 GitHub repository ruleset rule Protect main]
    • check-success = @github-actions/build
    • check-neutral = @github-actions/build
    • check-skipped = @github-actions/build

✅ Rule: Notify author on merge conflict (comment)

  • -closed
  • -draft
  • -merged
  • conflict

Rule: Flag package-lock.json changed without package.json (comment, label)

  • files~=^package-lock\.json$
  • -files~=^package\.json$

Rule: Flag package.json changed without package-lock.json (comment, label)

  • files~=^package\.json$
  • -files~=^package-lock\.json$

Rule: Flag invalid PR title format (comment, label)

  • -title~=^(feat|fix|docs|style|refactor|test|chore)(\(.+\))?!?:\s.+

Rule: Flag empty PR description (comment, label)

  • body~=^.{0,19}$

Rule: Flag missing linked issue (comment, label)

  • -body~=(?i)(closes?|fixes?|resolves?)\s+#[0-9]+
  • body~=.{20,}

Rule: Block merge when build fails (review)

  • check-failure = build
  • -author = dependabot[bot]

Rule: Comment when CodeRabbit requests changes (comment)

  • check-failure = CodeRabbit

Rule: Close PRs with no description (close)

  • body~=^\s*$
  • -author = coderabbitai[bot]
  • -author = dependabot[bot]

✅ Rule: Warn when branch is out of date (comment)

  • -author = dependabot[bot]
  • -draft
  • -linear-history

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

🚀  You can help us by becoming a sponsor!


1 not applicable rule

Rule: Auto-merge Dependabot PR (merge)

  • #commits-behind = 0 [🛡 GitHub repository ruleset rule Protect main]
  • -conflict [📌 merge requirement]
  • author = dependabot[bot]
  • check-success = Mergify Merge Protections
  • -closed [📌 merge requirement]
  • -draft [📌 merge requirement]
  • check-success = build
  • github-review-approved [🛡 GitHub repository ruleset rule Protect main]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [📌 merge requirement]
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections
  • any of: [🛡 GitHub repository ruleset rule Protect main]
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections
  • any of: [🛡 GitHub repository ruleset rule Protect main]
    • check-success = @github-actions/build
    • check-neutral = @github-actions/build
    • check-skipped = @github-actions/build
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