Skip to content

Commit

Permalink
Merge pull request #91 from fahadsNest/main
Browse files Browse the repository at this point in the history
fahadsnest
  • Loading branch information
daavid00 authored Dec 2, 2024
2 parents 373d30f + 35b83fa commit 77a0db9
Showing 1 changed file with 40 additions and 13 deletions.
53 changes: 40 additions & 13 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,18 +1,45 @@
# Contributing
Contributing to pyopmspe11

Hola hola 🙂.
The following is a set of guidelines for contributing to pyopmspe11.
First of all, thank you for considering contributing to pyopmspe11! This project thrives thanks to the amazing community of contributors like you. Whether you’re fixing bugs, adding new features, improving documentation, or reviewing pull requests, your help makes a real difference. So, let’s get started!

## Ground Rules
How to Contribute
We’ve made contributing as simple as possible, and we’d love for you to jump in. Here’s how you can get started:

1. We use Black code formatting
1. We use Pylint
1. We document our code
Fork the repository
Click the "Fork" button at the top right of this page to create a personal copy of pyopmspe11 on your GitHub account.

## Pull Request Process
Clone your fork
Now, clone your fork to your local machine. Open a terminal and run:

1. Work on your own fork of the main repo
1. Check that all the tests run
1. Check the code formatting and linting
1. Push your commits and make a pull request
1. The changes are merged when your code has been approved
bash
Copy code
git clone https://github.com/[your-username]/pyopmspe11.git
Set up your environment
Follow the instructions in the README to install any dependencies you'll need to run the project.

Create a new branch
It’s best to create a new branch for each change or feature you’re working on:

bash
Copy code
git checkout -b my-new-feature
Make your changes
Work on your code or documentation, and be sure to write meaningful commit messages.

Run tests (if applicable)
If your changes include code, make sure everything is working as expected by running the tests..

Commit your changes
Once you're happy with your changes, commit them:

bash
Copy code
git commit -m "Add feature X or fix bug Y"
Push your branch
Push your changes to your fork:

bash
Copy code
git push origin my-new-feature
Open a pull request
Now, go to the original pyopmspe11 repository and open a pull request from your fork. In your PR description, explain what you’ve done and why it’s important.

0 comments on commit 77a0db9

Please sign in to comment.