Vérifie si le linéaire est présent dans le périmètre de l'organisation

[mmarchois]

• Refs Restriction géographique pour la saisie des arrêtés #1212

Cette PR permet de restreindre la saisie d'une localisation au périmètre de son organisation compétente.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 42.85714% with 12 lines in your changes missing coverage. Please review.

Project coverage is 98.23%. Comparing base (75fb6bc) to head (7b59ee9).

Files with missing lines	Patch %	Lines
...Repository/Organization/OrganizationRepository.php	0.00%	12 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #1246      +/-   ##
============================================
- Coverage     98.35%   98.23%   -0.13%     
- Complexity     2133     2138       +5     
============================================
  Files           435      436       +1     
  Lines          9200     9221      +21     
============================================
+ Hits           9049     9058       +9     
- Misses          151      163      +12     

☔ 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.

[mmarchois]

@Lealefoulon merci pour la review, je vais rajouter quelques tests :)

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
16117795	Triggered	Generic Password	886771e	src/Infrastructure/Persistence/Doctrine/Fixtures/UserFixture.php	View secret
16117796	Triggered	Generic Password	886771e	src/Infrastructure/Persistence/Doctrine/Fixtures/UserFixture.php	View secret
16117797	Triggered	Generic Password	886771e	src/Infrastructure/Persistence/Doctrine/Fixtures/UserFixture.php	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}