-
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.
Bump Pre-Commit hook versions and adjust typing (#146)
- Loading branch information
1 parent
445ee5d
commit 99f6092
Showing
35 changed files
with
312 additions
and
201 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
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 |
---|---|---|
|
@@ -6,4 +6,4 @@ labels: "Question" | |
assignees: "" | ||
--- | ||
|
||
There is no stupid question. | ||
There are no stupid questions. |
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 |
---|---|---|
@@ -1,17 +1,34 @@ | ||
# Self review checklist ✅ | ||
|
||
Before creating a pull request you should check the following requirements that must be addressed before a PR will be accepted. | ||
Before creating a pull request you should check the following requirements that | ||
must be addressed before a PR will be accepted. | ||
|
||
- [ ] **All** pre-commit hooks must run through - successfully. | ||
- [ ] Make sure that the changes confirm the coding style of the [python-kraken-sdk](https://github.com/btschwertfeger/python-kraken-sdk). Most issues will be resolve through the pre-commit hooks. | ||
- [ ] Also take care to follow the community guidelines and the [Code of Conduct](./CODE_OF_CONDUCT.md). | ||
- [ ] Self-review your changes to detect typos, syntax errors and any kind of unwanted behavior. | ||
- [ ] If you changed the source code you have to **ensure that all unit tests run through**. If you added a new function you also have to **write a test** for that. Also make sure to **follow the doc string style** of the package and **provide at least one working example** within a function doc string. This is important since doc strings will be reflected within the documentation. | ||
- [ ] Take your time to prepare your code before creating a PR. A good PR will save a lot of time for everyone. | ||
- [ ] There are several workflows/actions within this repository. Any relevant workflow must be run successfully within your fork. In the following these workflows are listed, but **please also read the respective workflow files to get further information**. | ||
- PR Manual Pre-Commit (`manual_pre_commit.yaml`): This workflow must be green in any case. | ||
- [ ] Make sure that the changes confirm the coding style of the | ||
[python-kraken-sdk](https://github.com/btschwertfeger/python-kraken-sdk). Most | ||
issues will be resolve through the pre-commit hooks. | ||
- [ ] Also take care to follow the community guidelines and the [Code of | ||
Conduct](./CODE_OF_CONDUCT.md). | ||
- [ ] Self-review your changes to detect typos, syntax errors and any kind of | ||
unwanted behavior. | ||
- [ ] If you changed the source code you have to **ensure that all unit tests | ||
run through**. If you added a new function you also have to **write a test** | ||
for that. Also make sure to **follow the doc string style** of the package and | ||
**provide at least one working example** within a function doc string. This is | ||
important since doc strings will be reflected within the documentation. | ||
- [ ] Take your time to prepare your code before creating a PR. A good PR will | ||
save a lot of time for everyone. | ||
- [ ] There are several workflows/actions within this repository. Any relevant | ||
workflow must be run successfully within your fork. In the following these | ||
workflows are listed, but **please also read the respective workflow files to | ||
get further information**. | ||
- PR Manual Pre-Commit (`manual_pre_commit.yaml`): This workflow must be green | ||
in any case. | ||
- PR Manual Build (`manual_build.yaml`): Must be green in any case. | ||
- PR Manual CodeQL (`manual_codeql.yaml`): same here | ||
- PR Manual Test Spot (`manual_test_spot.yaml`): If any Spot related change happened | ||
- PR Manual Test Futures (`manual_test_futures.yaml`): For any Futures related changes | ||
- CI/CD (`cicd.yaml`): Can be used to run all actions at once - but requires having API keys for Spot, Futures and the Futures demo environment. | ||
- PR Manual Test Spot (`manual_test_spot.yaml`): If any Spot related change | ||
happened | ||
- PR Manual Test Futures (`manual_test_futures.yaml`): For any Futures related | ||
changes | ||
- CI/CD (`cicd.yaml`): Can be used to run all actions at once - but requires | ||
having API keys for Spot, Futures and the Futures demo environment. |
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
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.