Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: run commit message check after other lint checks #22208

Merged
merged 1 commit into from
Mar 15, 2021

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Mar 12, 2021

We recently had some lint failures slip into the main branch, because they had both commit message failures and other lint failures. The problem was that we sometimes ignore commit message failures since they can be fixed by the caretaker, but if the commit check fails, it prevents the other lint checks from running.

These changes move the commit message check to be last in the lint job so that if it fails, we know that everything else is in a mergeable state.

We recently had some lint failures slip into the main branch, because they had both
commit message failures and other lint failures. The problem was that we sometimes
ignore commit message failures since they can be fixed by the caretaker, but if the commit
check fails, it prevents any other the other lint checks from running.

These changes move the commit message check to be last in the `lint` job so that if it fails,
we know that everything else is in a mergeable state.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent merge safe target: patch This PR is targeted for the next patch release labels Mar 12, 2021
@crisbeto crisbeto requested a review from a team as a code owner March 12, 2021 08:05
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 12, 2021
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Mar 12, 2021
@mmalerba mmalerba merged commit 58118ec into angular:master Mar 15, 2021
mmalerba pushed a commit that referenced this pull request Mar 15, 2021
We recently had some lint failures slip into the main branch, because they had both
commit message failures and other lint failures. The problem was that we sometimes
ignore commit message failures since they can be fixed by the caretaker, but if the commit
check fails, it prevents any other the other lint checks from running.

These changes move the commit message check to be last in the `lint` job so that if it fails,
we know that everything else is in a mergeable state.

(cherry picked from commit 58118ec)
@angular-automatic-lock-bot
Copy link

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 Apr 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants