-
Notifications
You must be signed in to change notification settings - Fork 43
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
[CI:DOCS] nit: fix typo #1112
[CI:DOCS] nit: fix typo #1112
Conversation
Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
🤞 |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1112 +/- ##
==========================================
+ Coverage 33.69% 33.78% +0.08%
==========================================
Files 13 13
Lines 1119 1119
Branches 391 391
==========================================
+ Hits 377 378 +1
Misses 487 487
+ Partials 255 254 -1 |
@saschagrunert PTAL. This should be it 😄 |
ha, we didn't even need this PR, it's already triggered: https://copr.fedorainfracloud.org/coprs/rhcontainerbot/podman-next/build/5528574/ . So we're all set! |
btw, f36 builds are failing. If you don't care about f36 (like me), I can try disabling it for conmon-rs, but that may not work yet: packit/packit-service#1903 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lsm5, rphillips The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind other
What this PR does / why we need it:
Typo fix in comment. Also helps to check if packit builds are triggered on rhcontainerbot/podman-next copr after commit on main branch.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?