[ci] Add automated PR title check (#13867)

[aHenryJard]

Proposed changes

• Add a very permissive regexpr to check PR title.

Related issues

• closes Automatically check PR title with contributing.md format #13867

Checklist

• I consider the submitted work as finished
• I tested the code for its functionality
• I wrote test cases for the relevant uses case (coverage and e2e)
• I added/update the relevant documentation (either on github or on notion)
• Where necessary I refactored code to improve the overall quality

Further comments

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 31.11%. Comparing base (aa7bae1) to head (4314aeb).

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #13868   +/-   ##
=======================================
  Coverage   31.11%   31.11%           
=======================================
  Files        2920     2920           
  Lines      193545   193545           
  Branches    39497    39499    +2     
=======================================
+ Hits        60221    60227    +6     
+ Misses     133324   133318    -6     

Flag	Coverage Δ
opencti	31.11% <ø> (+<0.01%)	⬆️
opencti-front	2.49% <ø> (+<0.01%)	⬆️
opencti-graphql	68.55% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

This PR adds automated validation of pull request titles using a GitHub Actions workflow. The workflow enforces that PR titles follow the format [component] Message (#issuenumber) as specified in the CONTRIBUTING.md file.

Changes:

• Adds a new GitHub Actions workflow that triggers on PR open/edit events
• Uses the Slashgear/action-check-pr-title action to validate PR title format
• Provides a help message pointing to contribution guidelines

[Copilot]

The regex pattern has incorrect syntax. [[a-z]] should be \[[a-z] to match a literal opening bracket followed by lowercase letters. The pattern also doesn't match the closing bracket or validate the full format. A correct pattern would be: ^\[([a-z\-]+)\]\s+.+\s+\(#[0-9]+\)$ to match [component] Message (#issuenumber). The current pattern would incorrectly accept strings like [abc.

Suggested change

	regexp: "[[a-z]]+.+(#[0-9]+)"
	regexp: "^\\[([a-z\\-]+)\\]\\s+.+\\s+\\(#[0-9]+\\)$"

[Copilot]

Grammatical error in workflow step name. Should be 'follows' instead of 'follow' to match subject-verb agreement.

Suggested change

	name: Check that title follow convention
	name: Check that title follows convention

[Copilot]

Using pull_request_target trigger can be a security risk as it runs in the context of the base repository with access to secrets, even for PRs from forks. While the current permissions are set to contents: read which limits the risk, this trigger should only be used when necessary. Since this workflow doesn't need to post comments or access secrets (it just validates the title), using only pull_request trigger should be sufficient. If pull_request_target is needed for fork PRs, ensure this is intentional and documented.

Suggested change

	pull_request_target:
	types: [opened, edited]