[ci] Add issue linked verification (#13869)

[aHenryJard]

Proposed changes

• It's mandatory to have a linked issue on Pull Request, adding automation to check that automatically.

Example of message:

• Refactor PR checks to move them all in one workflow

Related issues

• closes Automatically check that there is an issue linked to a PR #13869

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

[github-actions]

Please attach at least one issue to your Pull Request

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 32.36%. Comparing base (39a8539) to head (73feb9e).
⚠️ Report is 12 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #13870   +/-   ##
=======================================
  Coverage   32.36%   32.36%           
=======================================
  Files        3096     3096           
  Lines      210891   210891           
  Branches    38200    38200           
=======================================
  Hits        68263    68263           
  Misses     142628   142628           

Flag	Coverage Δ
opencti-client-python	45.50% <ø> (ø)
opencti-front	2.83% <ø> (ø)
opencti-graphql	67.73% <ø> (ø)

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.

[ncarenton]

@aHenryJard This policy would be a great addition to improve traceability across our repositories. I would like to roll it out to other repos such as connectors, collectors, and injectors.

To avoid duplicating the logic everywhere, would it make sense to centralize the action in filigran-ci-tools ?

[aHenryJard]

@aHenryJard This policy would be a great addition to improve traceability across our repositories. I would like to roll it out to other repos such as connectors, collectors, and injectors.

To avoid duplicating the logic everywhere, would it make sense to centralize the action in filigran-ci-tools ?

I'm not sure it's a good idea to add a maintenance work to us when it's already done in a community. If there is some custom code why not, but when using directly a lib I don't see the benefit (more a pain of maintaining something in addition).

[github-actions]

Please attach at least one issue to your Pull Request

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.