Gitlab - Branch name

Published on Tue Mar 01 2022

Branch name for Gitlab's Push Rules

Additional matching regexes for
Gitlab - Branch name

Gitlab - Branch name

Branch name for Gitlab's Push Rules

Gitlab - Commit message

Commit message for Gitlab's Push Rules

@font-face stuff

bits and pieces of reusable replacements in CSS @font-face rules

Find missing or superfluous commas in "For å" constructions.

Finds missing commas in "For å ..." constructions according to officially ordained grammar-based comma rules.

BEST simple mail regex validator

# **VALIDATE ALL WOLRD MAIL RULES** 1. Very simple expression 2. Less than 140 caracters. 3. Validate on SonarQube typescript, javascript, angular rules # **EXAMPLES** [email protected],COM (INVALID) [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] (INVALID) [email protected] (INVALID)

Matching email addresses per RFC5322

The BNF rules from RFC 5322 transformed to PCRE by Nikita Popov and described in the post http://nikic.github.io/2012/06/15/The-true-power-of-regular-expressions.html.

MikroTik FireWall

Regex used in Splunk to extract fields from Mikrotik FW. NOTES: - Mikrotik must be configured to use "BSD Syslog" format - FW rules must add, as log prefix, the action: - drop - accep - reject - etc...

Password strength

Regular expression for password validation Rules: - 8-120 chars - no spaces - must contain at least one a-z char - must contain at least one A-Z char - must contain at least one digit - must contain at least one of the folowing chars: [email protected]#$%^&*()-=¡£_+`~.,<>/?;:'\"|[]{}

SoundCloud Link Verification

SoundCloud doesn't have usernames in their URLs, but the user can customize their url with the following rules for what comes after soundcloud.com/: • Use only numbers, lowercase letters, underscores, or hyphens. • Profile URLs must not start or end with an underscore or hyphen. • Profile URLs must not have two consecutive underscores or hyphens. • Profile URLs must be between 3 and 25 characters.

Password Enforcement Pattern -- trailing pattern

This RegEx was posted on a Ruby site as one for enforcing password pattern. I added {8,32} to limit the length of the password, even though I realize no one has passwords longer than that. Rules: at least 1 digit, 1 special character (as defined), 1 upper case and 1 lower case character, between 8 and 32 characters total. The question I have pertains to the trailing .*$ pattern. On the Rubular site, this is required. On regex101.com it does not see to add value to the regex. Do I need the .*$ on the expression?