I am not sure if this belongs here, but I am having an issue when using this Github Action.

This is the link to the github run that failed:
https://github.com/jampp/migratron/pull/25/checks?check_run_id=456554120

and the content is:

Uploading distributions to https://test.pypi.org/legacy/
Uploading migratron-1.1.0-py3-none-any.whl

  0%|          | 0.00/30.5k [00:00<?, ?B/s]
100%|

Is your feature request related to a problem? Please describe.

Given that both files and directories can be added using the files input which seems limited to describing files.

Describe the solution you'd like?

Proposed change here would be renaming files to paths which is more generic and can describe both file based paths and directories.

Describe alternatives you'v

Today Trivy does not offer the ability to display vulnerabilities while still returning a pass for the pipeline run

Example:
Project has 4 vulns: 2 high, 2 low, 0 critical
$ trivy fs --exit-code=1 --severity=CRITICAL .

What I got:
Trivy shows no vulnerabilities. Exit code 0.

What I want:
Show all vulnerabilities regardless of the level, still have an exit code of 0 as no

When using github job specific permissions and not allowing pr writes, this action should error.

I believe the issue is here:
https://github.com/repo-sync/pull-request/blob/master/entrypoint.sh#L84

Using || true will allow this command to succeed even during failure?

To recreate:

1. Make default action permission in repo = read-only
   `Settings -> Actions -> Workflow permissions -> R

whenever i push it repeats it. really annoying as i keep getting notifications for nothing.

This repository now has GitHub Issues enabled. It would be awesome to move https://github.com/jenkinsci/jenkinsfile-runner-github-actions#current-limitations--todos to GitHub issues so that potential contributors can see the issues and potentially contribute to them

Acceptance criteria

• Review the status of the TODO items
• Create issues for ones that are still actual. Some items need u