Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Nov 6, 2025

Closes:

The -s flag for frontmatter selectors only matches top-level YAML fields, not nested structures. This limitation was not documented.

Changes

Added clarification in four locations:

  • Features section: Inline note on "Frontmatter Filtering" feature
  • Options reference: Note under -s flag usage
  • How It Works: Example in filtering step showing language: go works, nested paths don't
  • Rule Files section: Explicit callout with ✅/❌ examples and workaround guidance

Example of the limitation:

---
language: Go        # ✅ Matches: -s language=Go
metadata:
  version: 1.0      # ❌ Cannot match: -s metadata.version=1.0
---

Users needing nested filtering should flatten their frontmatter structure to top-level fields only.

Original prompt

The current includes can only match top-level YAML fields. Highlight that in the docs.


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Co-authored-by: alexec <1142830+alexec@users.noreply.github.com>
Copilot AI changed the title [WIP] Update documentation to highlight top-level YAML fields Document that include selectors only match top-level YAML fields Nov 6, 2025
Copilot AI requested a review from alexec November 6, 2025 00:51
@alexec alexec marked this pull request as ready for review November 6, 2025 01:05
@alexec alexec enabled auto-merge (squash) November 6, 2025 01:05
@alexec alexec merged commit a1e5185 into main Nov 6, 2025
1 check passed
@alexec alexec deleted the copilot/highlight-top-level-yaml-fields branch November 6, 2025 01:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants