Adding --no-verify to git commit to ensure precommit hooks don't cause issues

[whoisarpit]

PR Checklist

• The commit message follows our guidelines: Code of conduct
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• Does this PR introduce a breaking change?
• Include PR in release notes?

PR Type

• Bugfix
• Feature
• Refactoring
• Build /CI
• Documentation
• Others

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Other information

[patched-admin]

The pull request under review involves a version update from 0.0.93 to 0.0.94 in the pyproject.toml file for the patchwork-cli package. While the diff only reflects a metadata change with no accompanying code modifications, it raises a broader concern regarding the use of the --no-verify flag with the git commit command. This flag bypasses commit hooks, which can lead to security vulnerabilities if essential checks are skipped, potential bugs if tests or linting are not executed, and deviations from coding standards that rely on these hooks for validation. Thus, while the current pull request is unlikely to introduce security or standard adherence issues, the risks associated with --no-verify necessitate careful consideration to ensure critical checks are preserved through alternative means if needed.

---

• File changed: patchwork/steps/CommitChanges/CommitChanges.py
  The addition of the --no-verify flag to the git commit command might introduce potential issues and security vulnerabilities. This flag bypasses commit hooks, which could lead to:

1. Security Vulnerability: Bypassing hooks could allow commits that do not pass necessary security checks that these hooks implement.
2. Potential Bugs: Commit hooks are often used to run tests or linting. Skipping these might introduce bugs that would have otherwise been caught.
3. Deviation from Standards: If the original coding standards rely on certain hooks for validation, this change would violate those standards.

It is advised to carefully consider the implications of using --no-verify and ensure that essential checks are maintained through other means if necessary.

• File changed: pyproject.toml
  The pull request only includes a version update from 0.0.93 to 0.0.94 in the pyproject.toml file for the patchwork-cli package. Since the diff only contains a version change, there are no code modifications to review for potential bugs, security vulnerabilities, or adherence to coding standards. This update seems to be a change in metadata, which typically does not introduce such issues.