-
Notifications
You must be signed in to change notification settings - Fork 19
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #243 from CPJKU/develop
Release 1.2.2
- Loading branch information
Showing
50 changed files
with
6,142 additions
and
326 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
name: Blacken code | ||
|
||
on: | ||
push: | ||
branches: | ||
- master | ||
pull_request: | ||
branches: | ||
- master | ||
jobs: | ||
format: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: actions/checkout@v2 | ||
- name: Format code with black | ||
run: | | ||
pip install black | ||
black --include="\.py,\.pyi" --exclude="env/*,tests/*" . | ||
- name: Commit changes | ||
uses: EndBug/add-and-commit@v4 | ||
with: | ||
author_name: ${{ github.actor }} | ||
author_email: ${{ github.actor }}@users.noreply.github.com | ||
message: "Format code with black" | ||
add: "." | ||
branch: ${{ github.ref }} | ||
- name: Notify errors | ||
if: failure() | ||
uses: dawidd6/action-send-mail@v2 | ||
with: | ||
server_address: smtp.gmail.com | ||
server_port: 465 | ||
username: ${{ secrets.EMAIL_USERNAME }} | ||
password: ${{ secrets.EMAIL_PASSWORD }} | ||
subject: "Format code with black" | ||
body: "Format code with black failed" | ||
to: ${{ secrets.EMAIL_TO }} | ||
from: ${{ secrets.EMAIL_FROM }} | ||
content_type: text/plain |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
name: Publish to PyPI.org | ||
on: | ||
release: | ||
types: [published] | ||
jobs: | ||
pypi: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- name: Checkout | ||
uses: actions/checkout@v3 | ||
with: | ||
fetch-depth: 0 | ||
- run: python3 -m pip install --upgrade build && python3 -m build | ||
- name: Publish package | ||
uses: pypa/gh-action-pypi-publish@release/v1 | ||
with: | ||
password: ${{ secrets.PYPI_API_TOKEN }} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
name: "Close stale issues and PRs" | ||
|
||
on: | ||
schedule: | ||
# Every day at 00:00 | ||
- cron: "0 0 * * *" | ||
workflow_dispatch: | ||
|
||
jobs: | ||
stale: | ||
runs-on: ubuntu-latest | ||
|
||
steps: | ||
- uses: actions/[email protected] | ||
with: | ||
stale-issue-message: 'This issue had no activity for **6 months**. It will be closed in **2 weeks** unless there is some new activity. Is this issue already resolved?' | ||
stale-issue-label: 'stale' | ||
exempt-issue-labels: 'bug,enhancement,good first issue' | ||
stale-pr-message: 'This pull request had no activity for **6 months**. It will be closed in **2 weeks** unless there is some new activity.' | ||
stale-pr-label: 'stale' | ||
days-before-stale: 180 | ||
days-before-close: 14 | ||
operations-per-run: 200 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,104 @@ | ||
# Contributing | ||
|
||
You can help the developers of **Partitura** by contributing, requesting features or reporting error. | ||
|
||
## Opening an Issue | ||
|
||
To open an issue navigate to the partitura github repository: | ||
|
||
[Repository]: https://github.com/CPJKU/partitura/issues "Partitura Issues Link" | ||
|
||
#### Click to **New Issue** | ||
|
||
![](docs/source/images/issue_page.png) | ||
|
||
#### Write your description | ||
|
||
![](docs/source/images/writing_issue.png) | ||
|
||
#### Choose the appropriate label | ||
|
||
![](docs/source/images/issue_choosing_label.png) | ||
|
||
##### How to choose your issue label: | ||
|
||
- **Question** to ask us a question or **help wanted** if you need a solution to a particular partitura problem. | ||
- **Bug** to report something not working correctly. | ||
- **Enhancement** to request for a feature. | ||
|
||
## How to contribute | ||
|
||
A step by step guide : | ||
|
||
1. To contribute is to open a relevant issue. | ||
2. ***Fork*** the Partitura repo. | ||
3. *Checkout* or *Pull* the latest stable develop branch. | ||
4. *Checkout a new branch* from the develop with the name of your develop idea. | ||
5. When finished coding, open a pull request to the develop branch of partitura. | ||
|
||
### Open a relevant issue | ||
|
||
Follow section how to open an issue. | ||
|
||
### **Fork** the Repo | ||
|
||
Fork partitura from | ||
https://github.com/CPJKU/partitura | ||
|
||
Once that you have already forked the repo, you can clone it: | ||
```shell | ||
git clone https://github.com/YourUsername/partitura.git | ||
cd partitura | ||
``` | ||
|
||
### Get latest Develop Branch | ||
|
||
```shell | ||
git fetch upstream | ||
git checkout develop | ||
git pull | ||
``` | ||
|
||
### Create your Branch | ||
|
||
```shel | ||
git checkout -b mycrazyidea | ||
``` | ||
|
||
Do your coding magic!!! | ||
|
||
Remember to commit regularly with descriptive messages about your changes. | ||
|
||
**!!! IMPORTANT NOTE !!!** | ||
|
||
Write Unit tests to check the compatibility and assure the evolution of your features. | ||
|
||
*Please follow instruction script found in the Tutorial repository.* | ||
|
||
### Opening your Pull Request | ||
|
||
##### Go to your forked Partitura repo and Click New Pull Request | ||
|
||
Open a Pull request from your new branch into the original `https://github.com/CPJKU/partitura` **develop** branch. | ||
|
||
Your pull request should then be visible on: | ||
|
||
[Partitura Pull Requests]: https://github.com/CPJKU/partitura/pulls "Partitura Pull Requests" | ||
|
||
![](docs/source/images/pull_requests.png) | ||
|
||
##### Set the base to develop and the compare to your branch | ||
|
||
![](docs/source/images/open_pull_request.png) | ||
|
||
##### Then create your Pull Request and add a description. | ||
|
||
When you create your PR then the partitura Unitests including the Unit Tests you wrote are ran. | ||
|
||
If there is no conflict with the develop branch then you will see this on your screen : | ||
|
||
![](docs/source/images/unitest_pass.png) | ||
|
||
If indeed the tests pass then a person from the development team of Partitura will review your work and accept your Pull Request. | ||
|
||
Your features will then be included to the next release of Partitura or a discussion will kick-start on your pull request thread. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.