fuzzyworld

explodorama / commit

Contributions by email: contrib-68uq+explodorama@fuzzyworld.net

8711e8e51f73bc9d5469ce6a075f95a75ef665ec · Pavel Safronov · 2026-10-26 21:55:53 -0700 · parents ba8e4ea0bb2d

Contributions by email: contrib-68uq+explodorama@fuzzyworld.net

CONTRIBUTING no longer says contributions are paused; branches and patches go to the contributions address, bug reports still through the in-game report link.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 CONTRIBUTING.md | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 335f4a3..f5315d7 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,10 +1,11 @@
 # Contributing to Explodorama
 
-Thank you for wanting to help! The project moved from GitLab to
+Thank you for wanting to help! The project lives at
 [code.fuzzyworld.net](https://code.fuzzyworld.net/explodorama/), which has no issue tracker or
-merge requests yet. Bug reports and playtest notes are welcome through the game's **report**
-link, which opens a prefilled email. Code contributions are paused until merge requests are
-supported again; the sections below still describe what one needs.
+merge requests. Bug reports and playtest notes are welcome through the game's **report**
+link, which opens a prefilled email. Code contributions arrive by email too: share a branch
+from any git host, or send a `git format-patch`, to `contrib-68uq+explodorama@fuzzyworld.net`
+([how to contribute](https://code.fuzzyworld.net/contribute/)).
 
 ## Reporting a bug
 
@@ -37,7 +38,7 @@ the game carries on instead of freezing.
 The URL parameters listed in the README (`?seed`, `?level`, `?charges`, `?dev`,
 `?immortal`, `?demo`) are the quickest way to reach the situation you are working on.
 
-## Before you send a change (once contributions reopen)
+## Before you send a change
 
 1. **`npm test` and `npm run build` both pass.** `npm run deploy` runs exactly these two,
    and only publishes when they pass.