CONTRIBUTING.md

Contributing to dileepa.dev

Thank you for your interest in contributing to dileepa.dev! We welcome any contributions, including bug fixes, feature enhancements, documentation improvements, and other general improvements.

Getting Started

1. Fork this repository to your GitHub account. This will create a copy of this repository in your account. You can make changes to this copy without affecting the original repository.

   • For fork this repository, click the Fork button in the top right corner of this page or click here.

2. Clone your forked repository to your local machine.

   • Use the following command to clone your forked repository to your local machine.

     git clone https://github.com/dileepadev/dileepa.dev.git

3. Create a new branch for your changes.

   • For example, to create a new branch named your-branch-name, use the following command and make sure to follow the branch naming guidelines.

     git checkout -b your-branch-name

4. Make your changes and commit them with a descriptive commit message.

   • For example, to commit your changes, use the following command and make sure to follow the commit message guidelines.

     git commit -m "feat: add a new feature"

5. Push your changes to your forked repository.

   • For example, to push your changes to your forked repository, use the following command.

     git push origin your-branch-name

6. Submit a pull request to the upstream repository.

   • For example, to create a pull request, use the following steps.
     1. Go to your forked repository.
     2. Click the Compare & pull request button next to your your-branch-name branch.
     3. Add a title and description for your pull request. Make sure to follow the pull request guidelines.
     4. Click Create pull request and remember to add the relevant labels with using the pull request template.

Guidelines

• Follow the code style of the project.
• Update the documentation if necessary.
• Add tests if applicable.
• Make sure all tests pass before submitting your changes.
• Keep your pull request focused and avoid including unrelated changes.
• Remember to follow the given files before submitting your changes.
  • bug_report.md - Use this template to create a report to help us improve.
  • feature_request.md - Use this template to suggest a feature for this project.
  • documentation_update.md - Use this template to propose a change to the documentation.
  • custom.md - Use this template to submit a custom issue.
  • PULL_REQUEST_TEMPLATE.md - Use this template to submit a pull request.
  • BRANCH_NAMING_GUIDELINES.md - Read this file to learn about the branch naming guidelines.
  • CHANGELOG.md - Read this file to learn about the changelog.
  • CODE_OF_CONDUCT.md - Read this file to learn about the code of conduct.
  • COMMIT_MESSAGE_GUIDELINES.md - Read this file to learn about the commit message guidelines.
  • CONTRIBUTING.md - Read this file to learn about the contributing guidelines.
  • LICENSE - Read this file to learn about the license.
  • PULL_REQUEST_GUIDELINES.md - Read this file to learn about the pull request guidelines.
  • README.md - Read this file to learn about the project.
  • SECURITY.md - Read this file to learn about the security policy.

Code of Conduct

Please note that this project adheres to the Contributor Covenant Code of Conduct. By participating in this project, you agree to abide by its terms.

Read the full code of conduct here.

Contact

If you have any questions, feel free to contact via GitHub Discussions.

Or, you can contact me via email at [email protected].