Skip to content

Latest commit

 

History

History
47 lines (31 loc) · 2.54 KB

CONTRIBUTING.md

File metadata and controls

47 lines (31 loc) · 2.54 KB

Contributing Guidelines

Welcome to my portfolio website! We appreciate your interest in contributing to my project. By contributing, you help me create a better software for everyone.

Before you start contributing, please take a moment to read the following guidelines to ensure a smooth and effective contribution process.

Table of Contents

  1. Getting Started
  2. How Can I Contribute?

Getting Started

  • Fork the repository on GitHub.
  • Clone your forked repository locally: git clone https://github.com/alvin-dennis/Personal-Portfolio-2.0.git
  • Change your directory to the project: cd <name>
  • Install project dependencies: npm install
  • Run in server: npm run dev

How Can I Contribute?

Reporting Bugs

If you find a bug, please ensure the bug was not already reported by searching on GitHub under Issues. If you can't find an existing issue addressing the problem, please open a new issue and provide detailed information about the bug.

Suggesting Enhancements

If you have an idea for an enhancement, we welcome your input. Before creating a new enhancement issue, please check the existing issues to see if your enhancement idea has already been discussed. If it hasn't, create a new issue and outline your enhancement proposal.

Working on Issues

Feel free to pick any open issue from our issue tracker that you find interesting. Comment on the issue that you would like to work on it so that others are aware you are addressing it. If you need more context on a particular issue, please ask for clarification.

Submitting Pull Requests

  1. Fork the repository and create your branch from main: git checkout -b your-branch-name
  2. Make your changes and test thoroughly.
  3. Add, commit, and push your changes to your forked repository.
  4. Create a pull request to the main branch of the original repository.
  5. Clearly describe your changes and why you think they should be merged.
  6. Be willing to make any requested changes or improvements.

Thank you for contributing! 🚀