Skip to content

TEMP: testing pytest-mh pr#8570

Open
spoore1 wants to merge 1 commit intoSSSD:masterfrom
spoore1:test_pytest_mh_pylibssh_logging_fix
Open

TEMP: testing pytest-mh pr#8570
spoore1 wants to merge 1 commit intoSSSD:masterfrom
spoore1:test_pytest_mh_pylibssh_logging_fix

Conversation

@spoore1
Copy link
Copy Markdown
Contributor

@spoore1 spoore1 commented Mar 31, 2026

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the system test requirements to use a personal fork of the pytest-mh library on a specific branch. Feedback indicates that referencing a personal fork and a branch name instead of a pinned commit SHA from an official repository poses a security risk and can lead to non-deterministic builds.

git+https://github.com/next-actions/pytest-importance
git+https://github.com/next-actions/pytest-mh
#git+https://github.com/next-actions/pytest-mh
git+https://github.com/spoore1/pytest-mh@pylibssh_logging_fix
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

security-high high

Referencing a personal fork and a branch name (spoore1/pytest-mh@pylibssh_logging_fix) instead of an official repository and a pinned commit SHA creates a security risk and potential for non-deterministic builds. Pin the dependency to a specific commit SHA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant