REGEXVAULTv2.0
Dev & Systems/Git
Verified Safe

Git Fully Qualified Ref Path Regex for Java

/^refs/(?:heads|tags|remotes|notes)/[a-zA-Z0-9][a-zA-Z0-9._\-/]{0,249}$/

What this pattern does

This page provides a well-structured, multi-part regular expression for matching git fully qualified ref path, ported and verified for Java. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your Java project — whether you're validating in a Spring Boot controller, a Jakarta EE service, or a standalone utility class.

Java Implementation

Java
// Git Fully Qualified Ref Path
// ReDoS-safe | RegexVault — Dev & Systems > Git

import java.util.regex.Pattern;

public class GitFullyQualifiedRefPathValidator {
    private static final Pattern PATTERN =
        Pattern.compile("^refs/(?:heads|tags|remotes|notes)/[a-zA-Z0-9][a-zA-Z0-9._\\-/]{0,249}$");

    public static boolean validate(String input) {
        return PATTERN.matcher(input).matches();
    }

    // Example
    public static void main(String[] args) {
        System.out.println(validate("refs/heads/main")); // true
    }
}

Test Cases

Matches (Valid)
Rejects (Invalid)
refs/heads/mainrefs/invalid/branch
refs/tags/v1.0.0heads/main
refs/remotes/origin/mainrefs/heads/../evil
refs/notes/commitsrefs/heads/branch with space
refs/heads/feature/my-branch

When to use this pattern

This pattern is drawn from the Dev & Systems > Git category and carries a ReDoS-safe certification. That matters for Java developers because critical in Java applications since the JVM regex engine uses backtracking and is susceptible to ReDoS without careful pattern design. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

Ref paths are filesystem paths internally. Path traversal via .. must be validated. Always sanitize user-provided ref path components.

Technical Notes

refs/heads/ = local branches. refs/remotes/ = tracking branches. refs/tags/ = tags. refs/notes/ = git notes. HEAD is a symbolic ref, not a standard ref path.

Have a pattern that belongs in the vault?

Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.

Submit a Pattern