2016-07-20 11:18:28 -04:00
|
|
|
%YAML 1.2
|
|
|
|
|
---
|
2021-03-23 22:19:59 +02:00
|
|
|
# Retired due to the following issues:
|
|
|
|
|
# 1. If the message contains commits from multiple authors, commits count per
|
|
|
|
|
# author is not available.
|
|
|
|
|
# 2. Even if commit count per author was available, there is no way to evaluate
|
|
|
|
|
# criteria separately for each author.
|
|
|
|
|
# 3. Synchronizing forks leads to the same commits being counted more than once.
|
2016-07-20 11:18:28 -04:00
|
|
|
|
|
|
|
|
# This is some metadata about the badge
|
|
|
|
|
name: Long Life to Pagure (Pagure V)
|
|
|
|
|
description: Pushed 500 commits to a Pagure repository.
|
|
|
|
|
creator: robyduck
|
|
|
|
|
|
|
|
|
|
# This is a link to the discussion about adopting this as a for-real badge.
|
2017-09-12 09:32:38 +02:00
|
|
|
discussion: https://pagure.io/design/issue/434
|
2016-07-20 11:18:28 -04:00
|
|
|
|
|
|
|
|
# A link to the image for the badge
|
|
|
|
|
image_url: https://badges.fedoraproject.org/pngs/pagure-long-life-500.png
|
|
|
|
|
# That's us!
|
|
|
|
|
issuer_id: fedora-project
|
|
|
|
|
|
|
|
|
|
# We'll perform our more costly check (defined below) only when
|
|
|
|
|
# we receive messages that match this 'trigger'
|
|
|
|
|
trigger:
|
|
|
|
|
topic: pagure.git.receive
|
|
|
|
|
|
|
|
|
|
# Once the check has been triggered, this defines what we actually check.
|
|
|
|
|
criteria:
|
|
|
|
|
datanommer:
|
|
|
|
|
filter:
|
|
|
|
|
topics:
|
|
|
|
|
- "%(topic)s" # The topic of the message that triggered us.
|
|
|
|
|
users:
|
2019-03-17 17:02:56 +01:00
|
|
|
- "%(msg.authors)s"
|
2016-07-20 11:18:28 -04:00
|
|
|
operation: count
|
|
|
|
|
condition:
|
|
|
|
|
greater than or equal to: 500
|
|
|
|
|
|
2019-03-17 17:02:56 +01:00
|
|
|
recipient: "%(msg.authors)s"
|