Git Remote URL (HTTPS) Regex for PHP
/^https://(?:[a-zA-Z0-9][a-zA-Z0-9\-]*\.)+[a-zA-Z]{2,63}/[a-zA-Z0-9_.\-]+/[a-zA-Z0-9_.\-]+(?:\.git)?$/iWhat this pattern does
This page provides a comprehensive, battle-tested regular expression for matching git remote url (https), ported and verified for PHP. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your PHP project — whether you're validating in a Laravel validator, a WordPress plugin, or a standalone PHP script.
Php Implementation
<?php
// Git Remote URL (HTTPS)
// ReDoS-safe | RegexVault — Dev & Systems > Git
define('GIT_REMOTE_URL_HTTPS_PATTERN', '/^https:\/\/(?:[a-zA-Z0-9][a-zA-Z0-9\-]*\.)+[a-zA-Z]{2,63}\/[a-zA-Z0-9_.\-]+\/[a-zA-Z0-9_.\-]+(?:\.git)?$/');
function validate_git_remote_url_https(string $input): bool {
return (bool) preg_match(GIT_REMOTE_URL_HTTPS_PATTERN, $input);
}
// Example
var_dump(validate_git_remote_url_https("https://github.com/user/repo")); // bool(true)Test Cases
Matches (Valid) | Rejects (Invalid) |
|---|---|
https://github.com/user/repo | git@github.com:user/repo.git |
https://github.com/org/repo.git | http://github.com/user/repo |
https://gitlab.com/group/project | https://github.com/user |
https://bitbucket.org/user/repo.git | github.com/user/repo |
https://git.example.com/team/project | — |
When to use this pattern
This pattern is drawn from the Dev & Systems > Git category and carries a ReDoS-safe certification. That matters for PHP developers because especially relevant in PHP where PCRE backtracking limits can trigger silent failures on malicious input. 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
GitHub, GitLab, and Bitbucket accept HTTPS URLs without .git. Some git server implementations require it. Strip .git before display but preserve it for git operations.
Technical Notes
The .git suffix is optional on all major hosting platforms. HTTP (non-TLS) should be rejected for security. Always use HTTPS for remote operations.
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