Skip to content

240.1-devcontainer-feature Create Automated Testing Workflow #247

Description

@codekiln

Task

Create GitHub Actions workflow for automated feature testing.

Context

Research (#241) shows that all production devcontainer features use automated CI testing with GitHub Actions. The workflow should trigger on changes to feature files and run comprehensive tests to validate feature installation and functionality.

Why this matters: Automated testing catches issues before they reach users and ensures the feature works across different environments.

Trigger Requirements

The workflow should trigger in two scenarios:

1. Feature Changes (PR Validation)

Test when feature files are modified to catch issues before merge.

2. Releases

Test when the langstar binary is released, as the devcontainer feature depends on it.

Release Process Context:

Recommended Triggers:

on:
  push:
    branches: [main]
    paths: ['.devcontainer/features/**']
    tags: ['v*']  # Test when binary releases happen
  pull_request:
    paths: ['.devcontainer/features/**']
  workflow_dispatch:  # Allow manual testing

Sub-tasks

  • Create .github/workflows/test-features.yml
  • Trigger on changes to .devcontainer/features/**
  • Trigger on PRs that modify feature files
  • Trigger on version tags (v*) when binary releases happen
  • Add manual trigger (workflow_dispatch) for testing
  • Set up workflow structure following devcontainers/features pattern

Research Reference

Lines 66-76 from research document (devcontainers/features approach)

Related Documentation

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions