Skip to content

🐛 fix(ci): separate tag and branch triggers in test-features workflow - #261

Closed
codekiln with Copilot wants to merge 3 commits into
codekiln/240-implement-automated-ci-testingfrom
copilot/sub-pr-260
Closed

🐛 fix(ci): separate tag and branch triggers in test-features workflow#261
codekiln with Copilot wants to merge 3 commits into
codekiln/240-implement-automated-ci-testingfrom
copilot/sub-pr-260

Conversation

Copilot AI commented Nov 24, 2025

Copy link
Copy Markdown
Contributor

Addresses review feedback on the test-features workflow trigger configuration and error handling.

Changes

Fixed trigger logic (.github/workflows/test-features.yml)

  • Separated tag trigger from branch trigger - Previously, the paths filter applied to both branches and tags, preventing tag-triggered runs since tags don't have associated file changes
  • Branch pushes to main now trigger only on feature file changes
  • Tag pushes (v*) always trigger to validate feature compatibility with releases

Added error handling for feature discovery

  • Check for .devcontainer/features directory existence before scanning
  • Handle empty features directory gracefully
  • Provide clear error messages for missing directories

Documentation improvements

Related

Addresses review comments from #260


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

codekiln and others added 3 commits November 24, 2025 06:53
Establishes foundational CI workflow structure for automated devcontainer
feature testing following production best practices from research (#241).

Changes:
- Created .github/workflows/test-features.yml
- Configured triggers:
  - Push to main (paths: .devcontainer/features/**)
  - Pull requests (paths: .devcontainer/features/**)
  - Version tags (v*) when binary releases happen
  - Manual workflow_dispatch for ad-hoc testing
- Set up OS matrix testing (Ubuntu 22.04, 24.04)
- Added Dev Container CLI installation
- Included feature discovery step
- Added placeholder for actual test implementation

Implementation Notes:
This workflow establishes the CI structure and triggers. Subsequent tasks
from parent issue #240 will implement the actual testing:
- #248: Dev Container CLI-based feature installation testing
- #249: OS distribution matrix testing (already scaffolded)
- #250: Smoke tests to verify langstar command
- #251: Feature metadata linting

Research Reference:
Based on devcontainers/features CI patterns documented in:
reference/research/241-devcontainer-feature-ci-testing/
devcontainer-feature-ci-testing-best-practices-2025-11-22.md (lines 66-90)

Fixes #247

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
- Separate tag trigger from branch trigger to fix path filter issue
- Add documentation comment explaining unused features output
- Add error handling for missing/empty features directory

Addresses Copilot review comments in PR #260

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Copilot AI changed the title [WIP] Create automated testing workflow for devcontainer features 🐛 fix(ci): separate tag and branch triggers in test-features workflow Nov 24, 2025
Copilot AI requested a review from codekiln November 24, 2025 12:11
Base automatically changed from codekiln/247-create-automated-testing-workflow to codekiln/240-implement-automated-ci-testing November 24, 2025 12:11
@codekiln codekiln closed this Nov 24, 2025
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