Ignore Rules

The sync module uses .iflowkit/ignore to filter IntegrationPackage differences before calculating changed artifacts.

File location

.iflowkit/ignore

What it affects

Ignore rules affect:

• sync push: which artifact is treated as changed
• sync compare: which differences are shown
• sync deliver: target branch vs tenant equality checks

They do not hide files from Git. Use .gitignore for Git-level ignore behavior.

Built-in defaults

The CLI includes built-in ignore defaults for noisy or generated files. You can also make these explicit in .iflowkit/ignore when you want the rule to be visible to the team.

Common examples:

metainfo.prop
parameters.prop

Pattern language

Supported behavior includes:

• * for a single path segment wildcard
• ** for recursive matching
• comments with #
• blank lines
• forward slash / as path separator

Windows-style backslashes should not be used.

Examples

Ignore all metainfo.prop files:

metainfo.prop

Ignore all parameters.prop files:

parameters.prop

Ignore a specific file in one iFlow:

IntegrationPackage/iFlows/MyFlow/META-INF/MANIFEST.MF

Ignore MANIFEST files in all iFlows:

IntegrationPackage/iFlows/**/META-INF/MANIFEST.MF

Ignore a generated cache tree:

IntegrationPackage/**/cache/**

Common mistakes

Confusing it with .gitignore

.iflowkit/ignore filters sync artifact detection. It does not prevent Git from tracking files.

Using backslashes

Use /, not \.

Expecting negation patterns

Negation rules such as !pattern are not documented as supported behavior. Keep rules simple and explicit.