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.

Sign up for GitHub

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

Jump to bottom

[pre-commit.ci] pre-commit autoupdate #136

Merged
merged 3 commits into from Mar 9, 2022
Merged

[pre-commit.ci] pre-commit autoupdate #136

merged 3 commits into from Mar 9, 2022

Conversation

pre-commit-ci[bot]
Copy link
Contributor

@pre-commit-ci pre-commit-ci bot commented Aug 23, 2021

@codecov
Copy link

codecov bot commented Aug 23, 2021 •
edited

Codecov Report

Merging #136 (563e45e) into master (e15bc85) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #136   +/-   ##
=======================================
  Coverage   92.69%   92.69%           
=======================================
  Files           2        2           
  Lines         219      219           
=======================================
  Hits          203      203           
  Misses         16       16
Flag Coverage Δ
pytests 92.69% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e15bc85...563e45e. Read the comment docs.

@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 1605bb3 to 6430162 Compare August 30, 2021 16:26
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch 2 times, most recently from 079e77d to 36b6736 Compare November 29, 2021 16:29
@pre-commit-ci
[pre-commit.ci] pre-commit autoupdate
d51b743 
updates:
- git://github.com/pre-commit/pre-commit-hooks: v4.0.1 → v4.1.0
- [github.com/mgedmin/check-manifest: 0.46 → 0.47](mgedmin/check-manifest@0.46...0.47)
- [github.com/psf/black: 21.7b0 → 22.1.0](psf/black@21.7b0...22.1.0)
- [github.com/PyCQA/pylint: v2.9.5 → v2.12.2](pylint-dev/pylint@v2.9.5...v2.12.2)
@eyllanesc eyllanesc mentioned this pull request Feb 20, 2022
Merged
@eyllanesc
Copy link
Contributor

eyllanesc commented Mar 1, 2022 •
edited

@foster999 If you wanted pre-commit.ci to re-execute the GA then it is not necessary to modify anything, it is enough for a user with write permissions like you to comment pre-commit.ci run. Read the docs:

re-running a pull request: you can trigger a re-run on a pull request by commenting pre-commit.ci run (must appear on a line by itself).

@foster999
Copy link
Collaborator

Thanks @eyllanesc, I wasn't sure if it would trigger out other Actions too. Will give it a try next time

@foster999 foster999 merged commit 709a43a into master Mar 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@foster999 foster999 foster999 left review comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@eyllanesc @foster999