REGEXVAULT
Dev & Systems/Git
ReDoS Checked

GitHub Actions Workflow Expression Regex for Java

/^\$\{\{\s+(?:github|env|vars|secrets|inputs|runner|job|steps|needs|matrix|strategy)(?:\.[a-zA-Z_][a-zA-Z0-9_\-]*)+\s+\}\}$/

All five implementations are free. Switch engines without signing in.

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching github actions workflow expression, 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
// GitHub Actions Workflow Expression
// ReDoS-checked | RegexVault — Dev & Systems > Git

import java.util.regex.Pattern;

public class GithubActionsWorkflowExpressionValidator {
    private static final Pattern PATTERN =
        Pattern.compile("^\\$\\{\\{\\s+(?:github|env|vars|secrets|inputs|runner|job|steps|needs|matrix|strategy)(?:\\.[a-zA-Z_][a-zA-Z0-9_\\-]*)+\\s+\\}\\}$");

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

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

Test Cases

Matches (Valid)
Rejects (Invalid)
${{ github.sha }}${{ unknown.context }}
${{ secrets.MY_SECRET }}${{ }}
${{ env.NODE_VERSION }}${{github.sha}}
${{ steps.build.outputs.artifact }}github.sha
${{ runner.os }}${ github.sha }

When to use this pattern

This pattern is drawn from the Dev & Systems > Git category and has been checked for ReDoS risk. 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

Never use ${{ github.event.pull_request.head.ref }} directly in shell commands — it allows script injection via branch names. Always use an intermediate environment variable.

Technical Notes

Requires at least two dot-separated components (context.property). Context names are lowercase in GitHub Actions. The i flag is not needed.

Have a pattern that belongs in the vault?

Submit it for review — community-verified patterns get credited to your GitHub handle. Submissions join the review queue after automated validation.

Submit a Pattern