It seems our maintainers like ci prefix for commits and PRs:
git log | grep 'ci:'
and

So let's document it.
It seems our maintainers like ci prefix for commits and PRs:
git log | grep 'ci:'
and

So let's document it.
Oh, I wasn't aware that build is used for ci changes as well. I saw ci mostly as a slightly more specific tests or qa.
Oh, I wasn't aware that
buildis used for ci changes as well. I sawcimostly as a slightly more specifictestsorqa.
Does it mean something like this:
- `test`, `qa` or `ci` for changes to the unit tests, QA tests or CI code
?
yes, CI refers to tests (it's a generalized "travis"), metadata such as .travis.yml and the things under the ci/ directory
(of course, this overlaps with "build" often, the categorization is by no means exclusive)
ACK 19267cbc82c1a09b37a0266b7bd930e9a62d1288 - this looks ok