From 0d2c62705c5c981822215e9605b64f073b2e8698 Mon Sep 17 00:00:00 2001 From: Michael Klishin Date: Tue, 5 Nov 2024 20:13:26 -0500 Subject: [PATCH] More CONTRIBUTING.md updates --- CONTRIBUTING.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9b256a778068..e3f6d19500e1 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -9,8 +9,8 @@ The process is fairly standard: * Present your idea to the RabbitMQ core team using [GitHub Discussions](https://github.com/rabbitmq/rabbitmq-server/discussions) or [RabbitMQ community Discord server](https://rabbitmq.com/discord) * Fork the repository or repositories you plan on contributing to - * Run `gmake` - * Create a branch with a descriptive name in the relevant repositories + * Run `git clean -xfffd && git clean && gmake distclean && gmake` to build all subprojects from scratch + * Create a branch with a descriptive name * Make your changes, run tests, ensure correct code formatting, commit with a [descriptive message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html), push to your fork * Submit pull requests with an explanation what has been changed and **why** * Submit a filled out and signed [Contributor Agreement](https://cla.pivotal.io/) if needed (see below) @@ -35,6 +35,7 @@ killall -9 beam.smp; killall -9 erl; killall -9 make; killall -9 epmd; killall - cd deps/rabbit # cleans build artifacts +git clean -xfffd gmake clean; gmake distclean # builds the broker and all of its dependencies