I made some art! http://threebean.org/bodhi-binary-star.svg

I made some art! http://threebean.org/bodhi-binary-star.svg

bodhi-binary-start 110x110

bodhi-binary-start 110x110

bodhi-binary-star 256x256

bodhi-binary-star 256x256

I imported Ralph's artwork into the master SVG, here are the exported PNGs

[[Image(bodhi-binary-star.png)]]
[[Image(bodhi-binary-star.2.png)]]

I imported Ralph's artwork into the master SVG, here are the exported PNGs

[[Image(bodhi-binary-star.png)]]
[[Image(bodhi-binary-star.2.png)]]

Here's a rule that should work for this:

``
%YAML 1.2

This is some metadata about the badge

name: Binary Star
description: You submitted a bodhi update including multiple packages.
creator: ralph

This is a link to the discussion about adopting this as a for-real badge.

discussion: https://fedorahosted.org/fedora-badges/ticket/4

A link to the image for the badge

image_url: http://infrastructure.fedoraproject.org/infra/badges/pngs/binary-star.png

That's us!

issuer_id: fedora-project

If we receive any bodhi message for which there is more than one build, then

award the badge to the submitter of that update.

trigger:
all:
- any:
- topic: bodhi.update.request.stable
- topic: bodhi.update.request.testing
- lambda: "len(msg.get('msg', {}).get('update', {}).get('builds', [])) > 1"

This criteria check could just be left empty since the trigger matching is all

that we need. We'll do something trivial just because fedbadges demands a

criteria block. We can remove this in the future.

criteria:
datanommer:
filter:
topics:
- "%(topic)s" # The topic of the message that triggered us.
users:
- "%(msg.update.submitter)s" # The user that was created.
operation: count
condition:
greater than or equal to: 1

recipient: "%(msg.update.submitter)s"
``

Here's a rule that should work for this:

``
%YAML 1.2

This is some metadata about the badge

name: Binary Star
description: You submitted a bodhi update including multiple packages.
creator: ralph

This is a link to the discussion about adopting this as a for-real badge.

discussion: https://fedorahosted.org/fedora-badges/ticket/4

A link to the image for the badge

image_url: http://infrastructure.fedoraproject.org/infra/badges/pngs/binary-star.png

That's us!

issuer_id: fedora-project

If we receive any bodhi message for which there is more than one build, then

award the badge to the submitter of that update.

trigger:
all:
- any:
- topic: bodhi.update.request.stable
- topic: bodhi.update.request.testing
- lambda: "len(msg.get('msg', {}).get('update', {}).get('builds', [])) > 1"

This criteria check could just be left empty since the trigger matching is all

that we need. We'll do something trivial just because fedbadges demands a

criteria block. We can remove this in the future.

criteria:
datanommer:
filter:
topics:
- "%(topic)s" # The topic of the message that triggered us.
users:
- "%(msg.update.submitter)s" # The user that was created.
operation: count
condition:
greater than or equal to: 1

recipient: "%(msg.update.submitter)s"
``

Done! https://badges.fedoraproject.org/badge/binary-star

Done! https://badges.fedoraproject.org/badge/binary-star

Set triaged to 'yes' for all tickets, as I've hit them all already.

Set triaged to 'yes' for all tickets, as I've hit them all already.

just put types back in, we'll try and handle bugs here too, no new trac.

just put types back in, we'll try and handle bugs here too, no new trac.