ci: set commit-lint step as optional #89
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Set the commit-lint CI step as optional.
As we're squashing the commits in all the Pull Requests and using the PR title as the new one, it is not actually relevent if the names of the PR commits are following the angular convention or not.
Motivation and Context
People contributing might not follow the Angular convention for the commit names, but at the end, what is important for us is the PR title (because of Squash & Merge). Examples:
#46
#47
How Has This Been Tested?
Test Case: the PR includes a commit not compliant with the Angular convention. Commit name: "Test optional step with non compliant commit"

Result: the step outcome is marked as success, while the error is displayed in the step details. More info about step context here
Screenshots (if appropriate):
Types of changes
Checklist: