github
/
apprise
mirror of https://github.com/caronc/apprise
1
0
Fork 0
Code Issues Releases Wiki Activity

Updated Development_Contribution (markdown)

master
Chris Caron 2025-07-28 20:31:10 -04:00
parent 115edeb700
commit 9b03504d00
1 changed files with 0 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
Development_Contribution.md

@ -35,23 +35,6 @@ merge your contributions smoothly.
- `packaging/`: You will find the MAN pages here and the SPEC files used to construct an RPM files - `packaging/`: You will find the MAN pages here and the SPEC files used to construct an RPM files
- `apprise/plugins/`: This is where Apprise plugins are found - `apprise/plugins/`: This is where Apprise plugins are found
If you prefer, sometimes it's easier to use the Docker containers to build your environment.
```bash
# The following would get you a shell that you could instantly leverage
# the local ./bin/apprise tool to test with (against code changes you make directly
# to the branch.
docker-compose run --rm test.py311 bash
# You can also run ./bin/checkdone.sh and ./bin/test.sh from here if you like as well
# The following is a great way to test your code to see if there is
# test coverage; there can not be an error when you create a pull request
docker-compose run --rm test.py311 bin/checkdone.sh
```
Note: `bin/checkdone.sh` does a full scan of the product where `test.sh` is a quick way to just test the code directly and also sectionaly test it.. hence `bin/test.sh discord` would only run the _discord related_ unit tests.
# Building Your Own Notification Plugin # Building Your Own Notification Plugin
It basically boils down to this: It basically boils down to this: