From 9b03504d0006d45c6133963abcb8d9b12f714c32 Mon Sep 17 00:00:00 2001 From: Chris Caron Date: Mon, 28 Jul 2025 20:31:10 -0400 Subject: [PATCH] Updated Development_Contribution (markdown) --- Development_Contribution.md | 17 ----------------- 1 file changed, 17 deletions(-) diff --git a/Development_Contribution.md b/Development_Contribution.md index afb4ba6..d6783f5 100644 --- a/Development_Contribution.md +++ b/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 - `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 It basically boils down to this: