Add comprehensive CONTRIBUTING.md file with devcontainer support to guide potential contributors

[Copilot]

• Create comprehensive CONTRIBUTING.md file with all essential sections
• Address initial feedback (build assets warning, simplified scripts and commits)
• Add comprehensive devcontainer documentation and setup instructions
• Include GITHUB_TOKEN setup requirements for testing
• Update release process to remove npm publication and focus on GitHub Actions workflow
• Update all npm test commands to npm run test for consistency and clarity

The CONTRIBUTING.md file now provides complete guidance for contributors with consistent command formatting throughout. All test commands now use the explicit npm run test format for better clarity and consistency.

---

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

[Copilot]

@virgofx 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs.

I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review.

[virgofx]

@copilot

• Explicitly state do not check in any build/distribution assets (e.g. npm run bundle) this is handled only for releases - testing is sufficient
• For key scripts, remove typecheck, bundle, and prettier. add test-watch
• for conventional commits, just refer to the website and leave intro overview (don't include subsections, e.g.
  format/types/examples)
• for PR process, again, remove bundle

[Copilot]

@copilot

• Explicitly state do not check in any build/distribution assets (e.g. npm run bundle) this is handled only for releases - testing is sufficient
• For key scripts, remove typecheck, bundle...

Updated CONTRIBUTING.md to address all your feedback points:

• Added explicit warning about not checking in build/distribution assets
• Updated key scripts section (removed typecheck, bundle, prettier; added test-watch)
• Simplified conventional commits to just reference the site without subsections
• Removed bundle from PR process workflow

Changes committed in c3b4906.

[virgofx]

@copilot

• prior to running tests in the container, ensure you specify and export GITHUB_TOKEN with a generic PAT from your user account.

• Additionally, can you provide somewhere near the top instructions for leveraging the built-in devcontainer support. This repo can be started with that.

• for the release process, remove npm package publication we don't do that. Instead, focus on saying releases are handled automatically via maintainers via the https://github.com/techpivot/terraform-module-releaser/actions/workflows/release-start.yml Release-Start/ Release workflow. In general, it generates a new pull request that builds (via npm run bundle) the assets, tags the appropriate version and generates a changelog automatically.

• add into the getting started section / top - the importance of devcontainers. The devcontainer is preconfigured and is the easiest way to get started. Research https://containers.dev/ and https://code.visualstudio.com/docs/devcontainers/containers to bring any insightful getting started with devcontainers for this project.

[Copilot]

@copilot

• prior to running tests in the container, ensure you specify and export GITHUB_TOKEN with a generic PAT from your user account.
  ...

Updated CONTRIBUTING.md with all requested enhancements:

• Added comprehensive devcontainer documentation as the recommended setup method with VS Code and Codespaces instructions
• Included GITHUB_TOKEN setup requirements in the testing section with export instructions
• Updated release process to remove npm package publication and focus on the Release-Start workflow that handles asset building automatically
• Reorganized Getting Started section to emphasize devcontainer support while maintaining manual setup option

Changes committed in 1aa4c2e.

[virgofx]

@copilot Ensure npm test is npm run test for clarity

[Copilot]

@copilot Ensure npm test is npm run test for clarity

Updated all instances of npm test to npm run test throughout the CONTRIBUTING.md file for consistency and clarity. Changed 6 occurrences across different sections including setup verification, development workflow, key scripts, warnings, testing instructions, and PR process.

Changes committed in the latest commit.

[virgofx]

@copilot Can you run npm run check:fix to ensure prettier runs and formats required files.

[Copilot]

@copilot Can you run npm run check:fix to ensure prettier runs and formats required files.

Ran npm run check:fix successfully. Biome checked 58 files and found no formatting issues - all files are already properly formatted according to the project's standards.

[github-actions]

📋 Release Plan

Module	Type	Latest Version	New Version	Release Details
tf-modules-kms	patch		1.0.0	🆕 Initial Release
tf-modules-vpc-endpoint	patch		1.0.0	🆕 Initial Release

📝 Changelog

tf-modules-kms-1.0.0 (2025-09-29)

• 🔀PR #249 - Add comprehensive CONTRIBUTING.md file with devcontainer support to guide potential contributors

tf-modules-vpc-endpoint-1.0.0 (2025-09-29)

• 🔀PR #249 - Add comprehensive CONTRIBUTING.md file with devcontainer support to guide potential contributors

_{Wiki Status^ℹ️}

✅ Enabled

_{Automated Tag/Release Cleanup^ℹ️}

⏸️ Existing tags and releases will be preserved as the delete-legacy-tags flag is disabled.

_{Powered by:   techpivot/terraform-module-releaser}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud