Feature: Advanced Triggers

[pepedinho]

Problem

Fleet currently only triggers pipelines when new commits are detected on remote branches.
This is useful but limited: some workflows require more flexible triggering conditions (e.g. scheduled jobs, manual execution, or reacting only to specific changes).

Proposed Solution

Introduce support for advanced trigger types in fleet.yml:

• Manual trigger: Allow running a specific job from CLI (fleet run <job>).
• Tag/branch filters: Trigger jobs only when specific branches or tags are updated.
• Path-based triggers: Trigger jobs only if certain files/directories have changed.

Example

triggers:
  push:
    branches: [main, develop]
    tags: [v*]

  manual: true

Acceptance Criteria

• Pipelines can be executed manually from CLI (fleet run <job>).
• Pipelines can filter execution by branch, tag, or path changes.
• Logs clearly indicate what trigger caused the pipeline to run.

Notes / Risks

• Ensure no infinite loops (e.g. pipeline modifying watched repo).