Added a tip for blueprints (#102)

* chore: Fixed formatting issues

* chore: Updated documentations

---------

Co-authored-by: ijlee2 <ijlee2@users.noreply.github.com>

Author: ijlee2

CONTRIBUTING.md

@@ -8,6 +8,7 @@ Here are some guidelines to help you and everyone else.
 ## Local development
 
 <details>
+
 <summary>Install dependencies</summary>
 
 1. Fork and clone this repo.
@@ -32,6 +33,7 @@ Here are some guidelines to help you and everyone else.
 
 
 <details>
+
 <summary>Lint files</summary>
 
 1. When you write code, please check that it meets the linting rules.
@@ -52,6 +54,7 @@ Here are some guidelines to help you and everyone else.
 
 
 <details>
+
 <summary>Run tests</summary>
 
 1. When you write code, please check that all tests continue to pass.
@@ -124,6 +127,7 @@ Here are some suggestions to help you start:
 
 
 <details>
+
 <summary>Give feedback 💞</summary>
 
 1. An open source project's value comes from people using the code and extending it to make greater things. Let me know how you use `@codemod-utils` in your codemod!
@@ -137,6 +141,7 @@ Here are some suggestions to help you start:
 
 
 <details>
+
 <summary>Help with marketing 📢</summary>
 
 1. Platforms include:
@@ -151,6 +156,7 @@ Here are some suggestions to help you start:
 
 
 <details>
+
 <summary>Join this project 👩‍💻👨‍💻</summary>
 
 1. Help me maintain the project! I have limited time and there is much that I don't know.
@@ -164,6 +170,7 @@ Here are some suggestions to help you start:
 
 
 <details>
+
 <summary>Make issues 📝</summary>
 
 1. In addition to sharing feedback (described in `Give feedback`), you can create an issue to:

README.md

@@ -29,8 +29,8 @@ npx @codemod-utils/cli --name <your-codemod-name>
 ## Tutorials
 
 - [Main tutorial](./tutorials/ember-codemod-rename-test-modules/00-introduction.md)
-- [Tutorial for blueprints](./tutorials/blueprint-for-v2-addon/00-introduction.md)
-- [Tutorial for `<template>`-tag components](./tutorials/template-tag-components/00-introduction.md)
+- [Blueprints](./tutorials/blueprint-for-v2-addon/00-introduction.md)
+- [`<template>`-tag components](./tutorials/template-tag-components/00-introduction.md)
 
 
 ## Codemods written with @codemod-utils

tutorials/blueprint-for-v2-addon/04-create-dynamic-files.md

@@ -270,7 +270,7 @@ workspace-root
 > [!IMPORTANT]
 > To create `.gitignore` and `.npmignore` via blueprints, the blueprint files must be named differently, e.g. `__gitignore__` and `__npmignore__`. Otherwise, these files will be missing in `src/blueprints` when the codemod is published.
 >
-> Afterwards, you can update `resolveBlueprintFilePath()` to handle `.gitignore` and `.npmignore`.
+> You might already see how to update `resolveBlueprintFilePath()` to handle `.gitignore` and `.npmignore`.
 >
 > ```diff
 > function resolveBlueprintFilePath(
@@ -286,6 +286,16 @@ workspace-root
 >     .replace('__testAppLocation__', testApp.location);
 > }
 > ```
+>
+> To double-check, run `pnpm publish --dry-run` and review the files.
+>
+> ```sh
+> npm notice 911B  dist/bin/blueprint-for-v2-addon.js
+> npm notice 145B  dist/src/blueprints/__addonLocation__/__gitignore__
+> npm notice 109B  dist/src/blueprints/__addonLocation__/.eslintignore
+> npm notice 340B  dist/src/blueprints/__addonLocation__/.eslintrc.js
+> ...
+> ```
 
 
 <div align="center">