Releases: MishaKav/pytest-coverage-comment
Releases · MishaKav/pytest-coverage-comment
Support `pull_request_target` event to add comments
What's Changed
Full Changelog: v1.1.43...v1.1.44
v1.1.43
What's Changed
- Export right
stms
when usingpytest-xml-coverage-path
, thanks to @ricardolsmendes for contribution - Fix some typos in comments
v1.1.42
What's Changed
- Bump eslint from 8.30.0 to 8.31.0 by @dependabot in #105
- Update comment with non default GitHub token by @MishaKav in #107
Full Changelog: v1.1.41...v1.1.42
Fix output of the `coverage`
Fix output of the coverage
when using only pytest-xml-coverage-path
Support GitHub enterprise urls
What's Changed
- Minor readme improvements by @AlexanderLanin in #100
- Support GitHub enterprise urls by @jbcumming in #101
New Contributors
- @AlexanderLanin made their first contribution in #100
Full Changelog: v1.1.39...v1.1.40
Support matrix with individual comments
What's Changed
Support matrix with individual comments. When you run in a matrix, and you want that every job will post a comment, you can use the unique-id-for-comment: ${{ matrix.python-version }}
. This will post a comment for every job, and will update them on every run.
New Contributors
- @dependabot made their first contribution in #97
Full Changelog: v1.1.38...v1.1.39
Fix when using `multiple-files` table is not formatted correctly
What's Changed
- Fix support for multiple-files without pytest reports by @jbcumming in #93
- Bump version and fix workflow permissions by @MishaKav in #95
New Contributors
- @jbcumming made their first contribution in #93
Full Changelog: v1.1.37...v1.1.38
Fix failing the action when the event type is not supported
- Fix failing the action when the event type is not
pull_request
/push
. Now it will just postwarning
message if you try to comment (and not fail the whole action). If you just using anoutput
of the action you will be able to run this action on events likeschedule
/workflow_dispatch
etc - Add full
CHANGELOG.md
(current file with all history). Those whos usedependabot
now will be able to see the changes directly in the PR
Upgrade node12 to node16
Upgrade node12 to node16
fix report-only-changed-files
v1.1.35 fix report-only-changed-files