From 16c5447228e2f8138b6dc90509e3310455bf9129 Mon Sep 17 00:00:00 2001 From: "Stanislav N. aka pztrn" Date: Wed, 1 Jan 2020 21:53:36 +0500 Subject: [PATCH] Clarified that every commit should contain full YouTrack issue ID for attaching. See this commit as example. SPEC-2 --- CPPs/proposed/CPP1 - CPP (Cadmium Protocol Proposal) flow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CPPs/proposed/CPP1 - CPP (Cadmium Protocol Proposal) flow.md b/CPPs/proposed/CPP1 - CPP (Cadmium Protocol Proposal) flow.md index 1a662f0..f7723f9 100644 --- a/CPPs/proposed/CPP1 - CPP (Cadmium Protocol Proposal) flow.md +++ b/CPPs/proposed/CPP1 - CPP (Cadmium Protocol Proposal) flow.md @@ -47,7 +47,7 @@ When preliminary stage is over and you've received "green light" for creating pu 5. Use template from ``cadmium-proposal-document-format.md`` placed in ``CPPs`` directory to describe your proposal in file created at step #3. 6. Push branch to git and create pull request to ``master`` branch. -Branch/commit will be automatically attached to YouTrack issue, so everyone interesting in it will receive notification and will be able to discuss your proposal. +To attach your commits into YouTrack issue please add full YouTrack issue ID (e.g. ``SPEC-123``) into commit message, otherwise commit might be lost and proposal might be eventually denied. **Please note that CPP ID you'll receive from core developer might not be the very same as issue ID in YouTrack.**