https://github.com/bzg/woof Skip to content Sign up Sign up * Why GitHub? Features - + Mobile - + Actions - + Codespaces - + Packages - + Security - + Code review - + Project management - + Integrations - + GitHub Sponsors - + Customer stories- * Team * Enterprise * Explore + Explore GitHub - Learn and contribute + Topics - + Collections - + Trending - + Learning Lab - + Open source guides - Connect with others + The ReadME Project - + Events - + Community forum - + GitHub Education - + GitHub Stars program - * Marketplace * Pricing Plans - + Compare plans - + Contact Sales - + Education - [ ] [search-key] * # In this repository All GitHub | Jump to | * No suggested jump to results * # In this repository All GitHub | Jump to | * # In this user All GitHub | Jump to | * # In this repository All GitHub | Jump to | Sign in Sign up Sign up {{ message }} bzg / woof * Notifications * Star 28 * Fork 1 Watch Over Our Folders EPL-2.0 License 28 stars 1 fork Star Notifications * Code * Issues 4 * Pull requests 0 * Actions * Projects 0 * Security * Insights More * Code * Issues * Pull requests * Actions * Projects * Security * Insights master Switch branches/tags [ ] Branches Tags Nothing to show {{ refName }} default View all branches Nothing to show {{ refName }} default View all tags 1 branch 10 tags Go to file Code Clone HTTPS GitHub CLI [https://github.com/b] Use Git or checkout with SVN using the web URL. [gh repo clone bzg/wo] Work fast with our official CLI. Learn more. * Open with GitHub Desktop * Download ZIP Launching GitHub Desktop If nothing happens, download GitHub Desktop and try again. Go back Launching GitHub Desktop If nothing happens, download GitHub Desktop and try again. Go back Launching Xcode If nothing happens, download Xcode and try again. Go back Launching Visual Studio If nothing happens, download the GitHub extension for Visual Studio and try again. Go back Latest commit @bzg bzg README.org: Tiny fix ... b3b5d14 Dec 14, 2020 README.org: Tiny fix b3b5d14 Git stats * 120 commits Files Permalink Failed to load latest commit information. Type Name Latest commit message Commit time src/bzg src/bzg/core.clj: Fix code typo Sep 17, 2020 test/bzg Handle series of patches Sep 16, 2020 .gitignore Let Git ignore .envrc May 31, 2020 LICENSE deps.edn: Add new metadata and update LICENSE to use EPL 2.0 May 25, 2020 README.org README.org: Tiny fix Dec 14, 2020 deps.edn deps.edn: Bump to version v0.2.1 Sep 15, 2020 pom.xml Bump version to 0.1.6 Sep 12, 2020 woof.png Update screenshot Sep 13, 2020 View code Woof! Basic usage Advanced usage Woof headers Announce a release Confirm a bug Confirm a bugfix Mark a patch as applied Request help Cancel a help request Announce a change Cancel a change Annotations for bugs and help requests Synonyms Configure Deploy Contribute Support the Clojure(script) ecosystem License README.org Woof! Woof! monitors updates sent to a mailing list. Plug Woof! to a mailbox subscribed to a mailing list, and Woof! will monitor updates about user-significant changes, help requests, bugs, patches and new releases. Subscribers of the list can trigger Woof! by using specific words either in the subject (for patches) or in the body (for bugs). All updates (for bugs, patches, help requests and new releases) can be triggered by using specific X-Woof-* mail headers. woof.png Basic usage Here are the triggers allows to manage bugs and patches: * Confirmed in the body of the email registers a new bug. * Fixed in the body of an email marks the bug in the same thread as fixed. * [PATCH] or [PATCH x/x] in the subject of a new email registers a new patch. * Applied in the body of an email marks the patch in the same thread as applied. Applied, Confirmed and Fixed should be placed at the beginning of a line in a plain-text email. Beware that the match is case-sensitive, so "applied", "CONFIRMED" and "FiXeD" won't work. Advanced usage You can control the Woof database entirely by adding headers in your replies to a mailing list. Woof headers X-Woof-Bug Confirm a bug. X-Woof-Help Request help. X-Woof-Change Announce a change. X-Woof-Release Announce a release. X-Woof-Patch Mark a patch as applied. Announce a release From: xxx@xxx.xx X-Woof-Release: 10.2 ... will declare 10.2 as a new release. Confirm a bug From: xxx@xxx.xx X-Woof-Bug: confirmed ... will mark a bug discussed in a thread as confirmed (see synonyms below.) Confirm a bugfix From: xxx@xxx.xx X-Woof-Bug: fixed ... will mark the bug discussed in a thread as fixed (see synonyms below.) Mark a patch as applied Any email with a subject containing a substring like [PATCH] or [PATCH x/x] will be referenced as proposing a new patch, without requiring a specific Woof! header. From: xxx@xxx.xx X-Woof-Patch: applied ... will mark a patch as applied. Request help From: xxx@xxx.xx X-Woof-Help: confirmed ... will add a request for help. Cancel a help request From: xxx@xxx.xx X-Woof-Help: canceled ... will cancel the help request from within this thread. Announce a change From: xxx@xxx.xx X-Woof-Change: 1234567879 8.4 ... will declare commit 1234567879 as an upcoming change for the future release version 8.4. When the 8.4 release is done, the change will not be advertized anymore. From: xxx@xxx.xx X-Woof-Change: 1234567879 8.4.2 8.5 ... will declare commit 1234567879 as an upcoming change for the future release versions 8.4 or 8.5. If, for any reason, version 8.4.2 is not released and version 8.5 is released instead, the change will not be advertized anymore. You can also omit the commit: From: xxx@xxx.xx X-Woof-Change: 8.4 ... Note that in this case, only one version is allowed. Cancel a change From: xxx@xxx.xx X-Woof-Change: cancel ... will cancel the change that was announced within this thread. Annotations for bugs and help requests By default, the summary for bugs and help requests is the subject of the email with the X-Woof-Bug or X-Woof-Help header. Sometimes, the subject of the email is not specific enough and you don't want to start a subthread by changing the subject while replying to a list. Instead, you can simply use the X-Woof-Bug or X-Woof-Help headers to add your summary. For example: From: xxx@xxx.xx X-Woof-Bug: X does Y instead of doing Z, as expected. ... will mark the bug discussed in a thread as confirmed and use X does Y instead of doing Z, as expected. as the summary for this bug. Synonyms * confirmed, true, t * canceled, cancel, closed, close, done, fixed, nil. Configure You need to set some environment variables to let the application run. See src/bzg/config.clj for the list of required variables. Run this to check your configuration: ~$ cd woof/ ~$ clj -A:test:runner Deploy ~$ cd woof/ ~$ clj -A:uberjar ~$ java -jar woof.jar Contribute Woof is alpha software. It is being tested to advertize updates from Org-mode but you should be able to use it for any project, provided that the maintainers on a mailing list agree to use Woof headers. That said, contributions are welcome! Support the Clojure(script) ecosystem If you like Clojure(script), please consider supporting maintainers by donating to clojuriststogether.org. License (c) Bastien Guerry 2020 Woof is released under the EPL 2.0 license. About Watch Over Our Folders Resources Readme License EPL-2.0 License Releases 10 tags Packages 0 No packages published Languages * Clojure 100.0% * (c) 2021 GitHub, Inc. * Terms * Privacy * Security * Status * Docs * Contact GitHub * Pricing * API * Training * Blog * About You can't perform that action at this time. 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.