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

chore(commit-lint): warn for body line length rule #46

Merged
merged 2 commits into from
Feb 1, 2024

Conversation

JAdshead
Copy link
Contributor

@JAdshead JAdshead commented Feb 1, 2024

Description

Change body-line-length rule to warn only.
This unblocks semantic release commits.

Motivation and Context

How Has This Been Tested?

Types of Changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation (adding or updating documentation)
  • Dependency update

Checklist:

  • My change requires a change to the documentation and I have updated the documentation accordingly.
  • My changes are in sync with the code style of this project.
  • There aren't any other open Pull Requests for the same issue/update.
  • These changes should be applied to a maintenance branch.
  • This change requires cross browser checks.
  • This change impacts caching for client browsers.
  • This change adds additional environment variable requirements for vitruvius users.
  • I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using vitruvius?

@JAdshead JAdshead requested a review from a team February 1, 2024 19:27
@10xLaCroixDrinker 10xLaCroixDrinker merged commit 22cf6dd into main Feb 1, 2024
3 checks passed
@10xLaCroixDrinker 10xLaCroixDrinker deleted the chore/commit-lint-warn-on-line-length branch February 1, 2024 21:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants