OutSystems deployments always include all actions and resources, even when some are:

• Debug or experimental
• Environment‑specific
• Not intended for higher environments

This increases deployment risk and forces developers to use workarounds (deleting, cloning modules, or manual discipline).

Proposed Solution

Introduce a way to exclude specific artifacts from deployment, similar to .gitignore.

Examples

• Mark Actions / Files / Folders as “Exclude from Deployment”
• Or define ignore rules per app/module (e.g. /Debug/*, /Resources/MockData.json)
• Optional: environment‑specific rules (Dev vs Prod)

Benefits

• Safer deployments
• Cleaner production environments
• Better DevOps and CI/CD workflows
• Less technical debt

This feature aligns with modern development practices and would greatly improve developer experience in OutSystems.