## TL;DR

Also check triggers: without a default: block, a push to a branch that matches no branches: block runs nothing, and pull-requests matches the SOURCE branch of the PR, not the destination. Validate the YAML locally before pushing with yaml.safe_load on the file.

## Fix

1. Also check triggers: without a default: block, a push to a branch that matches no branches: block runs nothing, and pull-requests matches the SOURCE branch of the PR, not the destination.
   Expected: You see the expected output instead of the problem.

## When to use

- You are setting up or using this Bitbucket Pipelines feature.
- The symptom matches: a single YAML artifact invalidates the whole config.

## When NOT to use

- Unrelated Bitbucket Pipelines issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Bitbucket Pipelines. Source: https://github.com/yoselingt/resuenawebapp/blob/HEAD/.claude/skills/deployment-skill/SKILL.md.

## Variant phrasings

### a single YAML artifact invalidates the whole config

## Why it happens

Bitbucket reports 'error in your bitbucket-pipelines.yml' and nothing runs. A stray artifact (copy-pasted tag, broken indentation, invalid anchor) kills the entire config, not just the affected step.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.

## Source

https://github.com/yoselingt/resuenawebapp/blob/HEAD/.claude/skills/deployment-skill/SKILL.md