From 54b57db329713289e8d4a1f3d0e853ee76b29f9b Mon Sep 17 00:00:00 2001 From: Athanasius Date: Mon, 7 Jun 2021 12:10:43 +0100 Subject: [PATCH] Contributing: // now mandated --- Contributing.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Contributing.md b/Contributing.md index 0dd7c1d6..f71d5673 100644 --- a/Contributing.md +++ b/Contributing.md @@ -129,12 +129,12 @@ Remember, you should always be working versus a single issue, even if the work i There might be cases where issues aren't duplicates, but your work still addresses more than one. In that case pick one for the naming scheme below, but mention all in commit messages and the Pull Request. -In all cases the branch should be named as per the scheme `<class>/<issue number>-<title>`: +In all cases the branch should be named as per the scheme `<class>/<issue number>/<title>`: * `<class>` - We have several classes of WIP branch: - * `fix` - For working on bug fixes, e.g. `fix/184-crash-in-startup` - * `enhancement` - For enhancing an *existing* feature, e.g. `enhancement/192-add-thing-to-wotsit` - * `feature` - For working on *new* features, e.g. `feature/284-allow-users-to-frob` + * `fix` - For working on bug fixes, e.g. `fix/184/crash-in-startup` + * `enhancement` - For enhancing an *existing* feature, e.g. `enhancement/192/add-thing-to-wotsit` + * `feature` - For working on *new* features, e.g. `feature/284/allow-users-to-frob` * `<issue-number>` is for easy reference when citing the issue number in commit messages. If you're somehow doing work that's not versus an issue then don't put the `<issue number>-` part in.