From 9985c86a72ab9776f9962ac36d577b151ed9af4e Mon Sep 17 00:00:00 2001 From: Nikolai Onken Date: Tue, 22 Mar 2016 16:59:47 +0100 Subject: [PATCH] Update CODING_STANDARDS.md --- docs/CODING_STANDARDS.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/CODING_STANDARDS.md b/docs/CODING_STANDARDS.md index e6b83592..c3d89f8d 100644 --- a/docs/CODING_STANDARDS.md +++ b/docs/CODING_STANDARDS.md @@ -700,13 +700,15 @@ Branch Naming We follow the uni-repo approach so our source is in one place. To work around some of the issues - for example looking at all PRs affecting a certain service - we prefix branches with the name of the service(s) the branch affects. - PR branch names, e.g. “api-”, “ide-”, “multi-ide-vfs-sapi-”. +PR branch names, e.g. + + “api-”, “ide-”, “multi-ide-vfs-sapi-” Checking for branch naming consistency is part of the review process and the teams responsibility. Use “all-” in case of doubt. E.g., https://github.com/c9/newclient/pull/12962/files affects redis schema code. -In case of doubt use `all-` as this indicates higher risk. Generally releasing changes affecting several services is a smell so this can help you identify possible issue. +Generally releasing changes affecting several services is a smell so this can help you identify possible issues. Other Resources ===============