CONTRIBUTING.md

Contributing to Git-trace 🎯

Contributions are what makes the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

Code of Conduct 📃

Please read and follow our Code of Conduct

Star our Repository ⭐

Need Help With The Basics? 🤔

If you're new to Git and GitHub, no worries! Here are some useful resources:

• Forking a Repository
• Cloning a Repository
• How to Create a Pull Request
• Getting Started with Git and GitHub
• Learn GitHub from Scratch

Project Structure 📂

GIT-TRACE/
├── .github/                  # GitHub-related configurations such as workflows, issue templates, etc
│   
├── app/                      # All the components included in the project
│   
├── components/               # All the .tsx files included in this
│   
├── helper/                   # Send mails section in the project
│     
├── lib/                      # All the typescript files
│   
├── prisma/                   # Prisma files included here
│   
├── public/                   # All the images which are used for the public references are included here 
│   
├── types/                    # Types .ts file included here
│   
├── .env.example          
│   
├── .eslintrc.json                  
│   
├── .gitignore
├──
├── CONTRIBUTING.md            # Instructions for the contributors
├──           
├── CODE_OF_CONDUCT.md         # Some rules for the contributors
├──
├── LICENSE                    # A permission to do something
├──
├── README.md                  # Some instructions regarding the contributions
├──
├── components.json
├──
├── middleware.js
├──
├── next-sitemap.config.js
├──
├── next.config.mjs
├──
├── package-lock.json
├──
├── package.json
├──
├── postcss.config.mjs
├──
├── tailwind.config.ts
├──
├── tsconfig.json

First Pull Request ✨

1. Star this repository Click on the top right corner marked as Stars at last.

2. Fork this repository Click on the top right corner marked as Fork at second last.

3. Clone the forked repository

git clone https://github.com/<your-github-username>/git-trace.git

4. Navigate to the project directory

cd git-trace

5. Create a new branch

git checkout -b <your_branch_name>

6. To make changes

git add .

7. Now to commit

git commit -m "add comment according to your changes or addition of features inside this"

8. Push your local commits to the remote repository

git push -u origin <your_branch_name>

9. Create a Pull Request

10. Congratulations! 🎉 you've made your contribution

Alternatively, contribute using GitHub Desktop 🖥️

1. Open GitHub Desktop: Launch GitHub Desktop and log in to your GitHub account if you haven't already.

2. Clone the Repository:

• If you haven't cloned the project repository yet, you can do so by clicking on the "File" menu and selecting "Clone Repository."
• Choose the project repository from the list of repositories on GitHub and clone it to your local machine.

3.Switch to the Correct Branch:

• Ensure you are on the branch that you want to submit a pull request for.
• If you need to switch branches, you can do so by clicking on the "Current Branch" dropdown menu and selecting the desired branch.

4. Make Changes:

• Make your changes to the code or files in the repository using your preferred code editor.

5. Commit Changes:

• In GitHub Desktop, you'll see a list of the files you've changed. Check the box next to each file you want to include in the commit.
• Enter a summary and description for your changes in the "Summary" and "Description" fields, respectively. Click the "Commit to " button to commit your changes to the local branch.

6. Push Changes to GitHub:

• After committing your changes, click the "Push origin" button in the top right corner of GitHub Desktop to push your changes to your forked repository on GitHub.

7. Create a Pull Request:

• Go to the GitHub website and navigate to your fork of the project repository.
• You should see a button to "Compare & pull request" between your fork and the original repository. Click on it.

8. Review and Submit:

• On the pull request page, review your changes and add any additional information, such as a title and description, that you want to include with your pull request.
• Once you're satisfied, click the "Create pull request" button to submit your pull request.

9. Wait for Review: Your pull request will now be available for review by the project maintainers. They may provide feedback or ask for changes before merging your pull request into the main branch of the project repository.

For Help And Support 💬

• Admin Github Profile:- (Rahul Sain)[https://github.com/rahulsainlll]
• Contact :- Email

House rules 🌐

• Before submitting a new issue or PR, check if it already exists in issues or PRs.
• If there isn't an issue please create one before any development begins
• GitHub issues: take note of the needs-approval label.
  • For Contributors:
    • Feature Requests / Refactoring on a Large Scale: Wait for an git-trace member to assign issue before you start coding or submitting a PR.
  • Our Process:
    • We greatly value new feature ideas. To ensure consistency in the product's direction, they undergo review and approval.

Developing 🔧

The development branch is main. This is the branch that all pull requests should be made against.

To develop locally:

1. Fork this repository to your own GitHub account and then clone it to your local device.

2. Create a new branch:

   git switch -c MY_BRANCH_NAME

Installing 📩

1. Set up the evn file just like .env.example
2. run npm install
3. run the development server: npm run dev

Building 🛠️

You can build the project with:

npx next build

If you get errors, be sure to fix them before committing.

Good Coding Practices 🧑‍💻

1. Follow the Project's Code Style

   • Maintain consistency with the existing code style (indentation, spacing, comments).
   • Use meaningful and descriptive names for variables, functions, and classes.
   • Keep functions short and focused on a single task.
   • Avoid hardcoding values; instead, use constants or configuration files when possible.

2. Write Clear and Concise Comments

   • Use comments to explain why you did something, not just what you did.
   • Avoid unnecessary comments that state the obvious.
   • Document complex logic and functions with brief explanations to help others understand your thought -process.

3. Keep Code DRY (Don't Repeat Yourself)

   • Avoid duplicating code. Reuse functions, methods, and components whenever possible.
   • If you find yourself copying and pasting code, consider creating a new function or component.

4. Write Tests

   • Write unit tests for your functions and components.
   • Ensure your tests cover both expected outcomes and edge cases.
   • Run tests locally before making a pull request to make sure your changes don’t introduce new bugs.

5. Code Reviews and Feedback

   • Be open to receiving constructive feedback from other contributors.
   • Conduct code reviews for others and provide meaningful suggestions to improve the code.
   • Always refactor your code based on feedback to meet the project's standards.

Making a Pull Request 🚀

• Be sure to check the "Allow edits from maintainers" option while creating your PR.
• If your PR refers to or fixes an issue, be sure to add refs #XXX or fixes #XXX to the PR description. Replacing XXX with the respective issue number. See more about Linking a pull request to an issue.
• Be sure to fill the PR Template accordingly.

Issue Report Process 📌

To report an issue, follow these steps:

1. Navigate to the project's issues section :- Issues
2. Please kindly choose the appropriate template according to your issue.
3. Provide a clear and concise description of the issue.
4. Wait until someone looks into your report.
5. Begin working on the issue only after you have been assigned to it. 🚀

Thank you for contributing 💗

We truly appreciate your time and effort to help improve our project. Feel free to reach out if you have any questions or need guidance. Happy coding! 🚀