Repository navigation
Provide specific scopes in contributing guidelines #4967
Description
This repository runs tests on Travis CI and AppVeyor. Although checking commit message, no one provides specific scopes in CONTRIBUTING.md.
Scope
The scope could be anything specifying place of the commit change. For example
Compiler,ElementInjector, etc.
Actually validate-commit-message.js checks scopes. If someone write wrong scopes in commit message, Travis CI and AppVeyor will fail. (me, too. at build #6536)
It's about time to provide specific scopes in CONTRIBUTING.md.
It looks like below.
### Scope
The scope could be anything specifying place of the commit change.
* @angular/cli
* @ngtools/json-schema
* @ngtools/logger
* @ngtools/webpack
* packaging
* changelog
Any thought?
Activity
clydin commentedon Feb 23, 2017
A documentation update is in progress.
comewalk commentedon Feb 24, 2017
@clydin sounds good 👍
angular-automatic-lock-bot commentedon Sep 6, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.