Merge pull request #40 from rishabh3562/feat/prettier-formatting-issue-39

style: apply Prettier formatting to entire codebase

Author: rishabh3562

.github/NEXT_STEPS.md

@@ -7,6 +7,7 @@ All changes have been successfully committed and pushed to your repository!
 **Commit**: `914e2b0` - fix(workflows): improve issue label detection and add label update tooling
 
 **Changes Pushed**:
+
 - ✅ Fixed Hacktoberfest workflow label detection logic
 - ✅ Created automated label update script
 - ✅ Added GitHub Actions workflow for easy updates
@@ -21,11 +22,13 @@ Your Hacktoberfest issues currently have incorrect "bug" labels. Follow these si
 ### Step 1: Go to GitHub Actions
 
 Open this link in your browser:
+
 ```
 https://github.com/rishabh3562/ToolBox/actions/workflows/update-labels.yml
 ```
 
 Or navigate manually:
+
 1. Go to https://github.com/rishabh3562/ToolBox
 2. Click the "Actions" tab
 3. Click "Update Issue Labels" in the left sidebar
@@ -51,6 +54,7 @@ After the workflow completes:
 2. You should see proper labels on all 20 Hacktoberfest issues:
 
 **Expected Label Distribution**:
+
 - `security` - Authentication and security issues (2 issues)
 - `database` - Storage and migration issues (1 issue)
 - `enhancement` - Feature requests (8 issues)
@@ -64,6 +68,7 @@ After the workflow completes:
 - `devops` - CI/CD and deployment (1 issue)
 
 **All issues will have**:
+
 - `hacktoberfest` label
 - `help wanted` label (where applicable)
 - `good first issue` label (where applicable)
@@ -73,13 +78,15 @@ After the workflow completes:
 ## 📊 What the Workflow Does
 
 The workflow will:
+
 1. ✅ Read your `.github/hacktoberfest-issues/ALL.md` file
 2. ✅ Find existing GitHub issues by matching titles
 3. ✅ Determine correct labels based on issue content
 4. ✅ Update labels via GitHub API
 5. ✅ Show summary of updates
 
 **Safe Operation**:
+
 - ❌ Will NOT recreate or delete issues
 - ❌ Will NOT modify issue titles or descriptions
 - ❌ Will NOT close any issues
@@ -91,25 +98,31 @@ The workflow will:
 ## 🔍 Monitoring the Workflow
 
 ### While Running:
+
 Click on the workflow run to see real-time logs:
+
 - "Update labels on existing issues" job
 - Watch as each issue is processed
 - See which labels are applied
 
 ### If Something Goes Wrong:
+
 The workflow includes detailed logging. Common issues:
 
 **"Issue not found"**
+
 - Issue title in ALL.md doesn't match GitHub issue title
 - Issue was deleted or renamed
 - Not a problem - workflow will continue with other issues
 
 **"Rate limit exceeded"**
+
 - Too many API calls
 - Wait 1 hour and re-run
 - Very unlikely with only 20 issues
 
 **"Permission denied"**
+
 - Repository permissions issue
 - Should not happen (workflow has correct permissions)
 - Contact GitHub support if this occurs
@@ -121,12 +134,14 @@ The workflow includes detailed logging. Common issues:
 After successful label updates:
 
 ### For Contributors:
+
 - Your issues will be properly categorized
 - Easier for Hacktoberfest participants to find relevant issues
 - Better filtering by label type
 - More accurate skill matching
 
 ### For Your Project:
+
 - Professional issue management
 - Clear organization for open source contributors
 - Better discoverability on GitHub
@@ -148,12 +163,15 @@ Both workflows are now available in your Actions tab!
 ## 🆘 Need Help?
 
 ### Documentation Available:
+
 - **Quick Start**: `.github/scripts/QUICK_START.md`
 - **Full Guide**: `.github/scripts/UPDATE_LABELS_README.md`
 - **Windows Guide**: `.github/scripts/RUN_ON_WINDOWS.md`
 
 ### Alternative Methods:
+
 If GitHub Actions doesn't work, you can also:
+
 1. Run the script locally (see RUN_ON_WINDOWS.md)
 2. Use GitHub CLI (see QUICK_START.md)
 3. Manually update labels (tedious, but possible)
@@ -163,6 +181,7 @@ If GitHub Actions doesn't work, you can also:
 ## ✨ Summary
 
 **What You Need to Do NOW**:
+
 1. Go to: https://github.com/rishabh3562/ToolBox/actions/workflows/update-labels.yml
 2. Click "Run workflow" → "Run workflow"
 3. Wait 30 seconds

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,9 +1,11 @@
 ## Description
-<!-- Provide a brief description of the changes in this PR -->
 
+<!-- Provide a brief description of the changes in this PR -->
 
 ## Type of Change
+
 <!-- Check all that apply -->
+
 - [ ] New tool addition
 - [ ] Tool improvement/update
 - [ ] Bug fix
@@ -13,21 +15,26 @@
 - [ ] Other (please describe):
 
 ## Related Issue
+
 <!-- Link to the issue this PR addresses -->
+
 Closes #
 
 ## Changes Made
-<!-- List the specific changes made in this PR -->
--
+
+## <!-- List the specific changes made in this PR -->
+
 -
 -
 
 ## Screenshots (if applicable)
-<!-- Add screenshots to demonstrate the changes -->
 
+<!-- Add screenshots to demonstrate the changes -->
 
 ## Tool Information (if adding a new tool)
+
 <!-- Fill this section only if you're adding a new tool -->
+
 - **Tool Name:**
 - **Category:**
 - **Website:**
@@ -36,13 +43,17 @@ Closes #
 - **Key Features:**
 
 ## Testing
+
 <!-- Describe how you tested your changes -->
+
 - [ ] I have tested the changes locally
 - [ ] All links are working and valid
 - [ ] Information provided is accurate and up-to-date
 
 ## Checklist
+
 <!-- Check all that apply -->
+
 - [ ] I have read the [CONTRIBUTING.md](../CONTRIBUTING.md) guidelines (if available)
 - [ ] My code follows the project's style guidelines
 - [ ] I have checked for duplicate tools/issues before submitting
@@ -51,11 +62,13 @@ Closes #
 - [ ] My changes do not introduce any breaking changes
 
 ## Additional Context
-<!-- Add any other context or information about the PR here -->
 
+<!-- Add any other context or information about the PR here -->
 
 ---
+
 **For Maintainers:**
+
 - [ ] Code review completed
 - [ ] Tests passed
 - [ ] Ready to merge