feature/ci-path-filtering - complete.

[garotm]

Thank you! Yes, the path filtering in the workflow configuration is a deliberate optimization to:

1. Only run CI when relevant files change:

# ios
paths:
  - 'ios/**'                     # Only when iOS code changes
  - '.github/workflows/ios.yml'  # Or when the workflow itself changes

# android
paths:
  - 'android/**'                     # Only when android code changes
  - '.github/workflows/android.yml'  # Or when the workflow itself changes

# python
paths:
  - 'backend/**'                     # Only when python code changes
  - '.github/workflows/build.yml'    # Or when the workflow itself changes
  - 'requirements*.txt'              # Or when the package requirements change

2. Save GitHub Actions minutes by not running unnecessary builds
3. Speed up PR merges by only running relevant checks

This is particularly useful in a monorepo structure like RunOn where we have:

• iOS frontend
• Backend Python code
• Android code (future)
• Infrastructure code

Each component has its specific workflow that only triggers when relevant files change. This way:

• Backend changes don't trigger iOS builds
• iOS changes don't trigger backend tests
• Each component can be developed independently
• CI/CD resources are used efficiently

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud