In the default branch mode, the action tries to push a commit to a new branch to upload the coverage report.
If the repository has conventional commits enabled, the action will fail, since the commit message doesn't adhere to the standard set by conventional commit.
Here is the line that causes the issue:
|
GIT_COMMIT_MESSAGE = "Update coverage data" |
And here is the issue in our pipeline:
Commit message must match a given regex pattern: (^Initial commit$)|(^((build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test|deploy){1}(\([\w\-\.]+\))?(!)?: ([\w ])+([\s\S]*)))Since this is a pretty standard code-quality feature in most repositories, a simple prefix in the comment would fix this problem, keeping the rest of the functionality the same.
In the default branch mode, the action tries to push a commit to a new branch to upload the coverage report.
If the repository has conventional commits enabled, the action will fail, since the commit message doesn't adhere to the standard set by conventional commit.
Here is the line that causes the issue:
python-coverage-comment-action/coverage_comment/storage.py
Line 25 in 4c2eefc
And here is the issue in our pipeline:
Since this is a pretty standard code-quality feature in most repositories, a simple prefix in the comment would fix this problem, keeping the rest of the functionality the same.