Updated examples in CONTRIBUTING.md to match currenty accepted convention e.g. [DOCS] {Verbose (50 char max) subject line}
Signed-off-by: Damian Williamson willtech@live.com.au
Updated examples in CONTRIBUTING.md to match currenty accepted convention e.g. [DOCS] {Verbose (50 char max) subject line}
Signed-off-by: Damian Williamson willtech@live.com.au
Updated examples in `CONTRIBUTING.md` to match currenty accepted convention e.g. [DOCS] {Verbose (50 char max) subject line}
Signed-off-by: Damian Williamson <willtech@live.com.au>Actually on PR titles I prefer github labels instead of prefixes, because a PR can affect multitple areas.
I still prefer prefix: to [prefix]. This is what linux, SDL, and many other projects use, I haven't ever seen the [xxx] convention for commits and I'm not sure why we need our own unique one.
So NACK on changing this.
Actually on PR titles I prefer github labels instead of prefixes, because a PR can affect multitple areas.
Contributors can't set these themselves. Labeling is up to the repo owners (possibly based on those hints). Also labels are per-PR and not per-commit.
I think prefixes are enough in commits (not against at all) and then someone with permissions (@fanquake for instance) set the correct labels on PR.
As for the prefix format, we should just use one.