mirror
/
c9-core
kopia lustrzana https://github.com/c9/core
1
0
Forkuj 0
Kod Zgłoszenia Packages Projekty Wydania Wiki Aktywność

Update CODING_STANDARDS.md

pull/284/head
Nikolai Onken 2016-03-22 16:59:47 +01:00
rodzic 6b1c373d4d
commit 9985c86a72
1 zmienionych plików z 4 dodań i 2 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

6
docs/CODING_STANDARDS.md
Wyświetl plik

@ -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. 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. 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. 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 Other Resources
=============== ===============