From 032ee29e14d591c2d9f3b0ec90251355b4cf6457 Mon Sep 17 00:00:00 2001 From: Michael Klishin Date: Thu, 27 Apr 2023 13:39:15 +0400 Subject: [PATCH] Update CONTRIBUTING.md to mention Bazel --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index da92446f6b..2a4fdce209 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -8,7 +8,7 @@ Pull requests is the primary place of discussing code changes. The process is fairly standard: * Fork the repository or repositories you plan on contributing to - * Run `make` + * Run `bazel sync` if you plan to [use Bazel](https://github.com/rabbitmq/contribute/wiki/Bazel-and-BuildBuddy), or `make` * Create a branch with a descriptive name in the relevant repositories * 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**