Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion .github/workflows/split-score.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@ on:
branches: [main]

permissions:
contents: read
pull-requests: write

jobs:
Expand All @@ -15,7 +16,8 @@ jobs:
with:
fetch-depth: 0

- uses: ./
- name: pr-split score
uses: vitali87/pr-split@v1.0.0

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Consider pinning to a commit SHA instead of a mutable tag

vitali87/pr-split@v1.0.0 is pinned to a tag, which is a mutable reference — the tag could be force-pushed to a different commit without changing this workflow file. GitHub's own security hardening guide recommends pinning third-party actions to a full commit SHA for supply-chain integrity.

Suggested change
uses: vitali87/pr-split@v1.0.0
uses: vitali87/pr-split@<full-commit-sha-of-v1.0.0>

You can find the SHA by running git ls-remote https://github.com/vitali87/pr-split refs/tags/v1.0.0 and using the dereferenced (^{}) object SHA.

Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/workflows/split-score.yml
Line: 20

Comment:
**Consider pinning to a commit SHA instead of a mutable tag**

`vitali87/pr-split@v1.0.0` is pinned to a tag, which is a mutable reference — the tag could be force-pushed to a different commit without changing this workflow file. GitHub's own security hardening guide recommends pinning third-party actions to a full commit SHA for supply-chain integrity.

```suggestion
        uses: vitali87/pr-split@<full-commit-sha-of-v1.0.0>
```

You can find the SHA by running `git ls-remote https://github.com/vitali87/pr-split refs/tags/v1.0.0` and using the dereferenced (`^{}`) object SHA.

How can I resolve this? If you propose a fix, please make it concise.

with:
max-loc: "400"
partition-strategy: "graph"
Expand Down
Loading