How to fix warning: no refs match pattern in Git

GitINTERMEDIATELOW

The git for-each-ref command returns no matches when the pattern provided doesn't match any existing references in the repository. This commonly occurs due to incorrect ref path patterns or shell quoting issues.

What this error means

The git for-each-ref command is designed to iterate over all refs that match a given pattern and display them in a specified format. When you see "no refs match pattern" or receive empty output, it means the pattern you provided doesn't correspond to any existing references in your repository. Unlike git branch which operates on short branch names (like "main" or "feature-branch"), git for-each-ref requires full reference paths. This means you need to specify the complete ref path like refs/heads/main instead of just main. The command uses fnmatch(3) pattern matching, which expects glob-style patterns with the full reference namespace. This behavior is by design - git for-each-ref silently returns empty results when patterns don't match, rather than throwing an error. This can be confusing when you're expecting results based on patterns that work with other Git commands.

How to fix "warning: no refs match pattern"

1Verify refs exist in your repository

First, check what refs are actually available in your repository:

bash

# List all refs
git for-each-ref

# List only branches
git for-each-ref refs/heads

# List only tags
git for-each-ref refs/tags

# List remote branches
git for-each-ref refs/remotes

This will show you the full ref paths and confirm refs exist before attempting pattern matching.

2Use full ref paths instead of short names

When filtering refs, always use the full reference path:

bash

# ❌ Wrong - short name won't work
git for-each-ref "main"
git for-each-ref "feature-*"

# ✅ Correct - use full ref path
git for-each-ref "refs/heads/main"
git for-each-ref "refs/heads/feature-*"

# For all branches containing "hotfix"
git for-each-ref "refs/heads/*hotfix*"

# For nested branches
git for-each-ref "refs/heads/**/*hotfix*"

The pattern must match against the complete ref name starting from refs/.

3Quote patterns properly for your shell

Shell interpretation of wildcards varies by shell type. Always quote patterns to prevent premature expansion:

bash

# Bash/sh - use single or double quotes
git for-each-ref 'refs/heads/*'
git for-each-ref "refs/heads/*"

# For options with wildcards (like --sort)
git for-each-ref '--sort=-*authordate' refs/heads

# Windows cmd.exe - use double quotes only
git for-each-ref "refs/heads/*"

On zsh and csh, unquoted wildcards in options (like --sort=-*authordate) will cause "no matches found" errors from the shell itself.

4Use --format to verify pattern matching

Add a format string to see exactly what refs are being matched:

bash

# Show ref names and author dates
git for-each-ref --format='%(refname) - %(authordate)' 'refs/heads/*'

# Show just the short ref names
git for-each-ref --format='%(refname:short)' refs/heads

# Count how many refs match
git for-each-ref --count=10 refs/heads

This helps debug whether your pattern is matching anything at all.

5Test with simplified patterns first

Start with broad patterns and narrow down:

bash

# Start broad - all branches
git for-each-ref refs/heads

# Add simple wildcard
git for-each-ref 'refs/heads/feature-*'

# Add complex glob patterns only after simple ones work
git for-each-ref 'refs/heads/**/release-*'

This helps identify whether the issue is with the pattern syntax or something else.

How to fix warning: no refs match pattern in Git

What this error means

Typical symptoms

Common causes

How to fix "warning: no refs match pattern"

Advanced notes

Related errors

Official resources & further reading