Skip to content

Commit

Permalink
DOC: Create CONTRIBUTING.md
Browse files Browse the repository at this point in the history
  • Loading branch information
Vini2 authored Mar 7, 2024
1 parent 9fa37c6 commit 72bb6d4
Showing 1 changed file with 101 additions and 0 deletions.
101 changes: 101 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,101 @@
# Contributing to ConDiGA project

We love to have your contributions to the ConDiGA project, whether it's:
* Reporting a bug
* Submitting a fix
* Proposing new features

## Clone and install ConDiGA onto your machine

First, make sure you have [git](https://github.com/git-guides/install-git) installed on your machine.

On GitHub, [fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) the ConDiGA repository and [clone](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository) it to your machine.

```bash
# clone repository to your local machine
git clone https://github.com/metagentools/ConDiGA.git
```

Move to the ConDiGA directory

```bash
cd ConDiGA
```

Create and activate the conda environment. Make sure to have [`conda`](https://docs.conda.io/en/latest/) installed.

```bash
# Create the condiga environment
conda env create -f build/environment.yml

# Activate the condiga environment
conda activate condiga
```

Now install ConDiGA via [`pip`](https://pip.pypa.io/en/stable/).

```bash
pip install -e .
```

## Test ConDiGA installation

Print the help message using the following command.

```bash
condiga -h
```

## Coding Style

We adhere to the [PEP 8](https://peps.python.org/pep-0008/) style guide.

Before committing, make sure to run [`black`](https://pypi.org/project/black/) and [`isort`](https://pypi.org/project/isort/).

```bash
black ./
isort --atomic ./
```

## Report bugs using GitHub's issues

We use GitHub issues to track public bugs. Report a bug by opening a new issue in GitHub [issues](https://github.com/metagentools/ConDiGA/issues). You will get to select between templates for bug report and feature request. If none of these templates match what you want to report, you can use the custom issue template.

## Committing code

Once you have finished coding and all the tests pass, commit your code and make a pull request.

```bash
# Add changed/added files
git add <file name>

# Commit changes
git commit -m "<commit message>"

# Push changes
git push
```

Make sure to follow the commit style of [c3dev](https://github.com/cogent3/c3dev/wiki#style-for-commit-messages). Relevant prefixes are replicated below for convenience.

| **Commit Prefix** | **For** |
|-------------------|-----------------------------------------------|
| DEV: | development tool or utility |
| DOC: | documentation |
| TST: | addition or modification of tests |
| REL: | related to a release |
| MAINT: | maintenance commit (refactoring, typos, etc.) |
| BUG: | bug fix |
| GIT: | git related |
| REV: | revert an earlier commit |


Your contribution will be reviewed before accepting it.

## License

By contributing, you agree that your contributions will be licensed under the MIT License.

## References

This document was adapted from the open-source contribution guidelines for [Transcriptase](https://github.com/briandk/transcriptase-atom/blob/master/CONTRIBUTING.md) and [c3dev](https://github.com/cogent3/c3dev/wiki/How-to-Contribute-Code).

0 comments on commit 72bb6d4

Please sign in to comment.