Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update pre-commit checks and add a couple of new ones #2835

Merged
merged 1 commit into from Apr 10, 2024

Conversation

happz
Copy link
Collaborator

@happz happz commented Apr 9, 2024

Namely prevent commits to main branch, check for merge/rebase conflict markers in files, and look for private keys.

Pull Request Checklist

  • implement the feature

@happz happz added no functional change "No Functional Change" intended. Patch should not change tmt's behavior in any way. tmt tests Improvements or additions to test coverage of tmt itself labels Apr 9, 2024
@happz happz added this to the 1.33 milestone Apr 9, 2024
Copy link
Collaborator

@lukaszachy lukaszachy left a comment

Choose a reason for hiding this comment

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

I'm surprised no fixup was necessary with checks added.

@martinhoyer
Copy link
Collaborator

Security-related checks note:
Skjold doesn't look like being suitable for pre-commit, as it checks .lock or .requirements.txt files.
Perhaps it would could be incorporated to the "without site packages" test.
pyproject.toml:

[tool.skjold]
sources = ["pyup", "gemnasium"] 
$ pip install .[all] skjold
$ pip list --exclude pip --format=freeze | skjold audit -
No vulnerable packages found!

@martinhoyer
Copy link
Collaborator

aand I don't see any other suitable (security) pre-commit hooks, so lgtm as is.

@lukaszachy
Copy link
Collaborator

aand I don't see any other suitable (security) pre-commit hooks, so lgtm as is.

@martinhoyer btw, could you tick the approval button - that would make github reviews counter happier.

@martinhoyer
Copy link
Collaborator

aand I don't see any other suitable (security) pre-commit hooks, so lgtm as is.

@martinhoyer btw, could you tick the approval button - that would make github reviews counter happier.

I'm not a reviewer on this one, so there is no approve button, but I'll keep it in mind for other PRs, thanks!

@psss
Copy link
Collaborator

psss commented Apr 10, 2024

I'm not a reviewer on this one, so there is no approve button, but I'll keep it in mind for other PRs, thanks!

@martinhoyer, I believe, everybody should be able to provide review. Even if not member of the organization / write access to the repo. See my recent review on the beakerlib pull request. You get a gray tick but the review is there.

@psss
Copy link
Collaborator

psss commented Apr 10, 2024

there is no approve button

You go to the Files changed tab and there's the Review changes button.

@martinhoyer
Copy link
Collaborator

there is no approve button

You go to the Files changed tab and there's the Review changes button.

Learning every day 🫡 Thanks.
(technically I wasn't wrong about the approve button though hehe)

Namely prevent commits to `main` branch, check for merge/rebase
conflict markers in files, and look for private keys.
@happz happz force-pushed the pre-commit-update-and-new-checks branch from 010340f to db4c34a Compare April 10, 2024 13:42
@happz happz added the full test Pull request is ready for the full test execution label Apr 10, 2024
@happz happz enabled auto-merge (squash) April 10, 2024 14:13
@happz happz merged commit 8cad364 into main Apr 10, 2024
18 of 20 checks passed
@happz happz deleted the pre-commit-update-and-new-checks branch April 10, 2024 19:04
skycastlelily pushed a commit to skycastlelily/tmt that referenced this pull request Apr 18, 2024
Namely prevent commits to `main` branch, check for merge/rebase
conflict markers in files, and look for private keys.
@lukaszachy lukaszachy modified the milestones: 1.33, 1.32.2 Apr 19, 2024
skycastlelily pushed a commit to skycastlelily/tmt that referenced this pull request Apr 23, 2024
Namely prevent commits to `main` branch, check for merge/rebase
conflict markers in files, and look for private keys.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
full test Pull request is ready for the full test execution no functional change "No Functional Change" intended. Patch should not change tmt's behavior in any way. tmt tests Improvements or additions to test coverage of tmt itself
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants