⚡ About Us:
This project is a URL Shortener application that allows users to enter a long URL, which is then shortened to a much shorter URL that can be easily shared. The shortened URL is redirectable to the original long URL. --## Table of Contents +
+ +
+
+
+⚡Tech Stack:
+
+ 
+ 
+ 
+ 
+ 
+ 
+
+
+
+
+
+
+ + +## ⚡Table of Contents: - [**Features**](#features) - [**Technologies**](#technologies) @@ -136,3 +152,81 @@ To use the app, follow these steps: 1. Enter a long URL in the input field and click the "Shorten" button. 2. Copy the shortened URL and share it with others. +
+ + + +
+
+
+
+ * **Checkout and make your changes for the develop branch only:** When working on your contributions, switch to the **develop** branch in your local repository. This ensures that you are working on the latest version of the codebase.
+
+* **Create pull requests only for the develop branch:** When you are ready to submit your changes, create a pull request (PR) targeting the **develop** branch. This allows the maintainers to review and merge your code into the main development branch.
+
+* **Maintain contribution guidelines:** Each project may have its specific contribution guidelines. It's important to familiarize yourself with these guidelines before submitting your contributions. Adhering to these guidelines ensures consistency and helps maintain the quality of the codebase.
+
+* **Format your commit message with the issue number:** When making commits related to an issue, follow the format **Fixes: #10 in your commit message. Replace 10 with the issue number you are addressing.** This helps track and manage issues more efficiently.
+
+* **Attach a Postman response screenshot for backend tasks:** For tasks related to the backend, it is recommended to include a screenshot of the Postman response along with your pull request. This provides additional context and helps reviewers understand the changes made and their impact on the backend functionality.
+
+* **Make your pull request descriptive and include examples:** When creating a pull request, provide a clear and descriptive explanation of the changes you made. This helps reviewers understand the purpose and significance of your contribution. Additionally, including at least one example that demonstrates the intended usage or effect of your changes can be beneficial.
+
+* **Rebase your commits and optimize file changes:** When submitting your pull request, consider rebasing your commits into one commit and optimizing your file changes. This helps keep the commit history clean and makes it easier for reviewers to understand your changes.
+
+Remember, following these guidelines will help ensure a smooth and efficient contribution process. Happy coding!
+
+
+
+⚡Contribution Guidelines:
+
+
+ * **Checkout and make your changes for the develop branch only:** When working on your contributions, switch to the **develop** branch in your local repository. This ensures that you are working on the latest version of the codebase.
+
+* **Create pull requests only for the develop branch:** When you are ready to submit your changes, create a pull request (PR) targeting the **develop** branch. This allows the maintainers to review and merge your code into the main development branch.
+
+* **Maintain contribution guidelines:** Each project may have its specific contribution guidelines. It's important to familiarize yourself with these guidelines before submitting your contributions. Adhering to these guidelines ensures consistency and helps maintain the quality of the codebase.
+
+* **Format your commit message with the issue number:** When making commits related to an issue, follow the format **Fixes: #10 in your commit message. Replace 10 with the issue number you are addressing.** This helps track and manage issues more efficiently.
+
+* **Attach a Postman response screenshot for backend tasks:** For tasks related to the backend, it is recommended to include a screenshot of the Postman response along with your pull request. This provides additional context and helps reviewers understand the changes made and their impact on the backend functionality.
+
+* **Make your pull request descriptive and include examples:** When creating a pull request, provide a clear and descriptive explanation of the changes you made. This helps reviewers understand the purpose and significance of your contribution. Additionally, including at least one example that demonstrates the intended usage or effect of your changes can be beneficial.
+
+* **Rebase your commits and optimize file changes:** When submitting your pull request, consider rebasing your commits into one commit and optimizing your file changes. This helps keep the commit history clean and makes it easier for reviewers to understand your changes.
+
+Remember, following these guidelines will help ensure a smooth and efficient contribution process. Happy coding!
+
++ + + + + +## :zap: Featured In: +
+
+
+
+
Open Source Programs
Code of Conduct:
License:
for this project!
+