Skip to content

chore(ci): validate the message of each new commit during ci#13815

Closed
matsko wants to merge 1 commit intoangular:masterfrom
matsko:gulp_lint_commit_message
Closed

chore(ci): validate the message of each new commit during ci#13815
matsko wants to merge 1 commit intoangular:masterfrom
matsko:gulp_lint_commit_message

Conversation

@matsko
Copy link
Copy Markdown
Contributor

@matsko matsko commented Jan 6, 2017

No description provided.

This patch adds the gulp command of `tools:validate-commit-message`
which will validate the range of commits messages present in the
active branch.
@matsko matsko force-pushed the gulp_lint_commit_message branch from 3df4a8e to dae8f49 Compare January 6, 2017 21:34
Comment thread gulpfile.js
});

gulp.task('tools:validate-commit-message', () => {
exec('git log --reverse --oneline HEAD ^upstream/master', (error, stdout, stderr) => {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't use upstream :(

Could we use the full name here instead of an alias so that everybody is happy ?

Comment thread tools/commit-message.json
"refactor",
"revert",
"style",
"test"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

build ?

@vicb
Copy link
Copy Markdown
Contributor

vicb commented Jan 6, 2017

What about using #9953 ?

IgorMinar added a commit to IgorMinar/angular that referenced this pull request Jan 20, 2017
This patch adds the gulp command of `validate-commit-messages`
which will validate the range of commits messages present in the
active branch.

This check now runs on CI as part of the linting checks.

Allowed commit message types and scopes are controlled via commit-message.json file
and documented at https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-commit-message-guidelines

This solution is based on old Vojta's code that he wrote for angular/angular.js, that was later adjusted
by @matsko in angular#13815.

Ideally we should switch over to something like https://www.npmjs.com/package/commitplease
as suggested in angular#9953 but that package currently doesn't support strict scope checking,
which is one of the primarily goal of this PR.

Note that this PR removes support for "chore" which was previously overused
by everyone on the team.

Closes angular#13815
Fixes angular#3337
@alxhub alxhub closed this in dff6ee3 Jan 23, 2017
@matsko matsko deleted the gulp_lint_commit_message branch March 1, 2017 18:49
juleskremer pushed a commit to juleskremer/angular that referenced this pull request Aug 28, 2017
This patch adds the gulp command of `validate-commit-messages`
which will validate the range of commits messages present in the
active branch.

This check now runs on CI as part of the linting checks.

Allowed commit message types and scopes are controlled via commit-message.json file
and documented at https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-commit-message-guidelines

This solution is based on old Vojta's code that he wrote for angular/angular.js, that was later adjusted
by @matsko in angular#13815.

Ideally we should switch over to something like https://www.npmjs.com/package/commitplease
as suggested in angular#9953 but that package currently doesn't support strict scope checking,
which is one of the primarily goal of this PR.

Note that this PR removes support for "chore" which was previously overused
by everyone on the team.

Closes angular#13815
Fixes angular#3337
@angular-automatic-lock-bot
Copy link
Copy Markdown

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.

@angular-automatic-lock-bot angular-automatic-lock-bot Bot locked and limited conversation to collaborators Sep 10, 2019
idlechara pushed a commit to idlechara/angular that referenced this pull request Apr 27, 2021
This patch adds the gulp command of `validate-commit-messages`
which will validate the range of commits messages present in the
active branch.

This check now runs on CI as part of the linting checks.

Allowed commit message types and scopes are controlled via commit-message.json file
and documented at https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-commit-message-guidelines

This solution is based on old Vojta's code that he wrote for angular/angular.js, that was later adjusted
by @matsko in angular#13815.

Ideally we should switch over to something like https://www.npmjs.com/package/commitplease
as suggested in angular#9953 but that package currently doesn't support strict scope checking,
which is one of the primarily goal of this PR.

Note that this PR removes support for "chore" which was previously overused
by everyone on the team.

Closes angular#13815
Fixes angular#3337
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants