You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!-- Please, make sure the following items are checked -->
4
+
Checklist before merging:
5
+
6
+
-[ ] Does this PR warrant a version bump? If so, make sure you add a git tag and GitHub release.
7
+
-[ ] Did you update the changelog with a user-readable summary? Please, include references to relevant issues or PR discussions. See [CII [release_notes] criterion](https://bestpractices.coreinfrastructure.org/en/criteria/0#0.release_notes_vulns).
8
+
-[ ] When adding new functionality: did you also add a test for it?
We welcome any kind of contribution to our software, from simple comment or question to a full fledged [pull request](https://help.github.com/articles/about-pull-requests/).
4
+
5
+
A contribution can be one of the following cases:
6
+
7
+
1. you have a question;
8
+
1. you think you may have found a bug (including unexpected behavior);
9
+
1. you want to make some kind of change to the code base (e.g. to fix a bug, to add a new feature, to update documentation);
10
+
1. you want to make a new release of the code base.
11
+
12
+
The sections below outline the steps in each case.
13
+
14
+
## You have a question
15
+
16
+
1. use the search functionality [here](https://github.com/spokenlanguage/platalea/issues) to see if someone already filed the same issue;
17
+
2. if your issue search did not yield any relevant results, make a new issue;
18
+
3. apply the "Question" label; apply other labels when relevant.
19
+
20
+
## You think you may have found a bug
21
+
22
+
1. use the search functionality [here](https://github.com/spokenlanguage/platalea/issues) to see if someone already filed the same issue;
23
+
1. if your issue search did not yield any relevant results, make a new issue, making sure to provide enough information to the rest of the community to understand the cause and context of the problem. Depending on the issue, you may want to include:
24
+
- the [SHA hashcode](https://help.github.com/articles/autolinked-references-and-urls/#commit-shas) of the commit that is causing your problem;
25
+
- some identifying information (name and version number) for dependencies you're using;
26
+
- information about the operating system;
27
+
1. apply relevant labels to the newly created issue.
28
+
29
+
## You want to make some kind of change to the code base
30
+
31
+
1. (**important**) announce your plan to the rest of the community *before you start working*. This announcement should be in the form of a (new) issue;
32
+
1. (**important**) wait until some kind of consensus is reached about your idea being a good idea;
33
+
1. if needed, fork the repository to your own Github profile and create your own feature branch off of the latest master commit. While working on your feature branch, make sure to stay up to date with the master branch by pulling in changes, possibly from the 'upstream' repository (follow the instructions [here](https://help.github.com/articles/configuring-a-remote-for-a-fork/) and [here](https://help.github.com/articles/syncing-a-fork/));
34
+
1. make sure the existing tests still work by running ``tox``;
35
+
1. also make sure you do not diverge from PEP8 standards by fixing any issues flake8 reports in the ``tox`` run; if you do diverge, make sure you clearly explain why;
36
+
1. add your own tests (if necessary);
37
+
1. update or expand the documentation;
38
+
1. push your feature branch to (your fork of) the platalea repository on GitHub;
39
+
1. create the pull request, e.g. following the instructions [here](https://help.github.com/articles/creating-a-pull-request/).
40
+
41
+
In case you feel like you've made a valuable contribution, but you don't know how to write or run tests for it, or how to generate the documentation: don't let this discourage you from making the pull request; we can help you! Just go ahead and submit the pull request, but keep in mind that you might be asked to append additional commits to your pull request.

5
+
[](https://github.com/spokenlanguage/platalea/actions/workflows/pythonapp.yml)
0 commit comments