chore: adding an ignore step to the docs update pipelines to avoid ov…

[dotkas]

Pull Request Submission Checklist

• [x] Follows CONTRIBUTING guidelines
• [x] Commit messages are release-note ready, emphasizing what was changed, not how.
• [x] Includes detailed description of changes
• [x] Contains risk assessment (Low | Medium | High)
• [ ] Highlights breaking API changes (if applicable)
• [ ] Links to automated tests covering new functionality
• [ ] Includes manual testing instructions (if necessary)
• [ ] Updates relevant GitBook documentation (PR link: ___)
• [ ] Includes product update to be announced in the next stable release notes

What does this PR do?

Stops the full test pipeline if only docs-related changes are being merged, as these automated docs-update steps waste a lot of resources and time, such as: https://github.com/snyk/cli/pull/5979

A step was also added to block attempts to cheat the pipeline by just naming the branch accordingly 😸

Where should the reviewer start?

The CircleCI orb.

How should this be manually tested?

Create a bash script with the relevant changes and try to commit things to your branch that does not follow the rules, and run the script.

What's the product update that needs to be communicated to CLI users?

None, internal CI/CD optimization.

[snyk-io[bot]]

:tada: Snyk checks have passed. No issues have been found so far.

:white_check_mark: security/snyk check is complete. No issues have been found. (View Details)

:white_check_mark: license/snyk check is complete. No issues have been found. (View Details)

:white_check_mark: code/snyk check is complete. No issues have been found. (View Details)

[github-actions[bot]]

	Warnings
:warning:	"chore: adding an ignore step to the docs update pipelines to avoid over-testing" is too long. Keep the first line of your commit message under 72 characters.

Generated by :no_entry_sign: dangerJS against a3f932e7c997cf1e9ac6053865d98418cb413839