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

intelmqsetup: fix typo in message #2181

Merged
merged 1 commit into from
May 31, 2022
Merged

Conversation

sebix
Copy link
Member

@sebix sebix commented May 23, 2022

intelmqsetup: fix typo in message

@sebix sebix added bug Indicates an unexpected problem or unintended behavior component: core labels May 23, 2022
@sebix sebix added this to the 3.1.0 milestone May 23, 2022
@codecov-commenter
Copy link

codecov-commenter commented May 23, 2022

Codecov Report

Merging #2181 (8639be4) into develop (ce60fd4) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff            @@
##           develop    #2181   +/-   ##
========================================
  Coverage    76.34%   76.34%           
========================================
  Files          441      441           
  Lines        23649    23649           
  Branches      3739     3739           
========================================
  Hits         18055    18055           
  Misses        4857     4857           
  Partials       737      737           
Impacted Files Coverage Δ
intelmq/bin/intelmqsetup.py 0.00% <0.00%> (ø)

Copy link
Contributor

@waldbauer-certat waldbauer-certat left a comment

Choose a reason for hiding this comment

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

LGTM

@sebix sebix merged commit f98d0a7 into certtools:develop May 31, 2022
@sebix sebix deleted the typo-intelmqsetup branch May 31, 2022 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or unintended behavior component: core
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants