ci(github): commit parity to use PR title in check
Primary Changes
---------------
1. Updated the script to include the check for releases
2. Fixed certain regex and added a new regex for issue/PR
references. This is done because the issue numbers tagged in
PR message or commit messages are sometime resolved directly
and sometimes parsed with the orgname.
3. With the new regex in 2), we can now safely check for parity
while including the fixes/depends line, further loosing the parity
check, thus reducing false-positives
Fixes #3526
Pull Request Requirements
[ ] Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
[ ] Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
[ ] Follow the Commit Linting specification. You may refer to this link for more information.
Character Limit
[ ] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
[ ] Commit Message per line must not exceed 80 characters (including spaces and special characters).
A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.
Commit to be reviewed
ci(github): commit parity to use PR title in check
Fixes #3526
Pull Request Requirements
upstream/mainbranch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.-sflag when usinggit commitcommand. You may refer to this link for more information.Character Limit
A Must Read for Beginners For rebasing and squashing, here's a must read guide for beginners.