Add GitHub Actions workflow for packaging, testing, and Node.js compatibility analysis

[Copilot]

Implements CI automation for qmd with package distribution, cross-runtime testing, and Node.js migration analysis.

Workflow Jobs

Package - Creates distributable tarball with installation files, uploads as artifact (30d retention)

Test (Bun) - Primary test suite execution on Bun runtime with log artifacts

Test (Node.js) - Matrix testing across v18/v20/v22. Expected to fail due to Bun-specific APIs (bun:sqlite, bun:test, Glob/$). Captures failure modes for compatibility tracking.

Node.js Compatibility Analysis - Static analysis of Bun API usage with migration paths:

• bun:sqlite → better-sqlite3
• bun:test → vitest/jest
• Glob API → fast-glob
• Shell $ → execa

Generates detailed report artifact (90d retention).

CI Status - Aggregates results. Passes if package + Bun tests succeed; Node.js results are informational.

Triggers

• Push to main
• Pull requests
• Manual dispatch

Security

Explicit contents: read permissions at workflow and job level. CodeQL clean.

Files Changed

• .gitignore - Remove .github/ exclusion
• .github/workflows/ci.yml - New 301-line workflow

Original prompt

Create a GitHub Actions workflow file to facilitate the automation of packaging, testing, and checking Node.js compatibility for the qmd project. Key requirements for the workflow include:

1. Packaging for Installation:

   • Package the qmd project to make installation easier.
   • Ensure compatibility with the specific requirements of the repository.

2. Unit Tests:

   • Run unit tests using both Bun and Node.js environments.
   • Include matrix testing for multiple versions of Node.js.
   • Ensure that all dependencies are correctly installed for both environments.

3. Node Compatibility Assessments:

   • Perform any additional checks or validations to see how close the qmd project is to supporting Node.js compatibility natively. Include tasks or logs to highlight compatibility roadblocks.

4. Job Triggering:

   • Trigger the workflow on pull requests, pushes to the main branch, or manual triggers (workflow_dispatch).

5. Results:

   • Provide clear messages indicating the success or failure of each job.
   • Save or upload artifacts if needed (e.g., logs, packaged files) for debugging or future reference.

This pull request was created from Copilot chat.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.