File: CONTRIBUTING.md

package info (click to toggle)
antimeridian 0.4.6-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 14,964 kB
  • sloc: python: 1,172; sh: 8; makefile: 4
file content (35 lines) | stat: -rw-r--r-- 1,437 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
# Contributing

First off, thanks for contributing to **antimeridian**!
We appreciate it.

## Reporting a bug

1. Go to <https://github.com/gadomski/antimeridian/issues/new>
2. Create a new issue.
   Please provide as much information as you can about the problem, including your system, the source file, and any error messages.

## Requesting a feature

1. Go to <https://github.com/gadomski/antimeridian/issues/new>
2. Create a new issue that describes the feature that you'd like to see, with as much detail as possible.

We will do our best to review and provide feedback on any feature requests, but know that it might take a while.

## Fixing or adding something

1. Hack away (see the [Developing](./README.md#developing) section of the README for how to get started).
2. Fork this repo to your own account.
3. Push your branch to your repo.
4. Open a pull request (PR) against <https://github.com/gadomski/antimeridian>.

We'll do our best to review your PR in a timely fashion.
Here's some things to include your PR to make our lives easier:

- A good description of what you're adding or fixing
- Tests to demonstrate the bug you're fixing, or to exercise the feature you're adding
- Documentation about the new feature, if applicable
- A [CHANGELOG](./CHANGELOG.md) entry
- Well-organized git history, where each commit is one self-contained set of work

Don't bother with bumping the version number, we'll do that ourselves.