Skip to content

CONTRIBUTING: Drop dev branch #145

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 30, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 10 additions & 10 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,20 +4,20 @@

When contributing to this repository, please first discuss the change you wish to make with an issue.

- Ideas are a valuable source of contributions others can make
- Problems show where this project is lacking
- With a question you show where contributors can improve the project
- Before opening a new issue, make sure there is not an existing one about your same problem/request.
- Please use, when possible, use the issue templates.
- Ideas are a valuable source of contributions others can make
- Problems show where this project is lacking
- With a question you show where contributors can improve the project
- Before opening a new issue, make sure there is not an existing one about your same problem/request.
- Please use, when possible, use the issue templates.

## Pull Requests

You should be clear which problem you're trying to solve with your
contribution.

### When making a pull request:
### When making a pull request

1. Fork the dev branch of this repository.
2. Make your changes addressing one thing at the time with meaningful commit messages
4. Update the README or config template as needed
5. Try to keep Pull requests short and concise focused in one aspect of the project at the time
1. Fork this repository.
2. Make your changes addressing one thing at a time with meaningful commit messages
3. Update the README or config template as needed
4. Try to keep Pull requests short and concise focused in one aspect of the project