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

Fix the mailman_schema example to work with Message.body #135

Merged
merged 1 commit into from Feb 28, 2019

Conversation

jeremycline
Copy link
Member

The message body variable is used by the Message class, but the
example schema is still defining a property using that name.

See https://pagure.io/fedora-commops/fedora-happiness-packets/issue/96

Signed-off-by: Jeremy Cline jcline@redhat.com

@abompard
Copy link
Member

Could you run Black and rebase please?

The message ``body`` variable is used by the Message class, but the
example schema is still defining a property using that name.

See https://pagure.io/fedora-commops/fedora-happiness-packets/issue/96

Signed-off-by: Jeremy Cline <jcline@redhat.com>
@codecov-io
Copy link

codecov-io commented Feb 28, 2019

Codecov Report

Merging #135 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #135   +/-   ##
=======================================
  Coverage   96.92%   96.92%           
=======================================
  Files          13       13           
  Lines        1106     1106           
  Branches      155      155           
=======================================
  Hits         1072     1072           
  Misses         24       24           
  Partials       10       10

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 c838f2a...9394ad5. Read the comment docs.

@mergify mergify bot merged commit 60e2395 into fedora-infra:master Feb 28, 2019
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.

None yet

3 participants