Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(Scaffold): keep template file name #56

Merged

Conversation

jeffersondanielss
Copy link
Collaborator

@jeffersondanielss jeffersondanielss commented Feb 13, 2025

Clingon CLI logo

Clingon Empire | Official Pull Request

Fill in the fields appropriately so that empire reviewers can validate your work.


Important

Do not publish using local npm, with each PR the Release CI pipeline is executed, ensuring version control, publication and creation of the release and changelog.

Warning

Don't forget to put the correct label before creating the PR, so that auto does not create canaries for code that it doesn't need (docs, internal, etc.) and versioning correctly for the code that needs to be published. To learn about labels, check the following documentation: Auto Release.


Description

keep template file name in generated files

Requirements

I did:

  • Unit tests
  • Code formatting
  • Documentation with JSDocs
  • (Optional) Documentation with Markdown
  • Documentation on github.com/ipetinate/clingon-dot-dev
  • Local Tests
  • I tested the canary release
  • I marked the Issue referring to the code (if you didn't create the branch from the issue)

Preview

Canary Release

@ipetinate ipetinate merged commit 97c5190 into ipetinate:main Feb 14, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants