Skip to content

Conversation

@Shipra-Singh-Asd
Copy link
Collaborator

Summary

Explain the change in 1–3 sentences. Reference any related issues (e.g. Closes #123).

Type of Change

  • πŸš€ Feature (feat:) - New functionality for users
  • πŸ› Bug fix (fix:) - Fixes an issue for users
  • ⚠️ Breaking Change (feat!: or fix!:) - Changes that break backward compatibility
  • πŸ“š Docs (docs:) - Documentation updates only
  • πŸ”§ Chore / Refactor (chore:, refactor:) - Internal changes, no user impact
  • πŸ§ͺ Tests (test:) - Test additions or updates
  • πŸš€ CI / Build (ci:) - Build system or CI changes
  • πŸ“¦ Dependencies (deps:) - Dependency updates
  • πŸŽ‰ Other - Changes that don't fit the above categories

Release Notes Impact

  • User-facing change - Should be included in release notes
  • Internal change only - No need to include in release notes

Motivation / Context

Why is this change needed? What problem does it solve or what capability does it add?

Approach

Briefly describe how you implemented the change. Note any notable design decisions, trade-offs, or alternatives considered.

CLI Impact

If this alters user-facing CLI behavior:

  • Added / changed flags? Describe.
  • Backward compatible? If breaking, explain migration path.
  • Sample invocation before vs after:
# before
# after

Generated Output Impact

List any new / modified scaffold files or structural differences (e.g. new template folder, changed Dockerfile pattern, compose changes, new preset behaviors).

Tests

Describe test coverage:

  • Added new test(s)
  • Updated existing test(s)
  • Manually smoke-tested locally
  • No tests needed (explain why)

If you ran the smoke scaffold locally, paste the command & confirm success:

node bin/index.js demo --services node --no-install --yes

Result: βœ… / ❌

Breaking Changes & Migration

Breaking changes:

Migration steps:

Configuration changes needed:

Screenshots / Logs (Optional)

Add any helpful output (chalk-styled CLI messages, error reproduction, etc.).

Docs

  • Updated README.md if needed
  • Updated .github/copilot-instructions.md if internal conventions changed
  • Added/updated relevant documentation for user-facing changes
  • Not applicable

Checklist

  • Code follows existing style (chalk usage, emoji prefixes, exit codes)
  • No accidental large asset additions outside templates/
  • Default ports preserved / conflicts handled
  • New service templates added to: choices array, defaultPorts, Dockerfile switch, compose mapping
  • Git history clean (no stray debug commits)
  • Dependency additions are minimal & justified

Open Questions / Follow-ups

List any TODOs or future enhancements not in this PR.


Thanks for contributing! πŸŽ‰

@Shipra-Singh-Asd Shipra-Singh-Asd merged commit 42467ed into main Nov 16, 2025
14 checks passed
@Shipra-Singh-Asd Shipra-Singh-Asd deleted the sharedLibrary branch November 16, 2025 13:29
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.

Feature: Language-specific shared libs (Python package, Go module)

3 participants