A Quarkus-powered GitHub App that regularly sends short lists of GitHub issues/PRs for triagers/maintainers/stewards to consider.
This GitHub App is based on the Quarkus GitHub App framework.
It periodically extracts GitHub issues/PRs from one "source" GitHub repository (e.g. https://github.com/quarkusio/quarkus) and notifies maintainers about them by commenting on GitHub issues in another "notification" GitHub repository (e.g. https://github.com/quarkusio/quarkus-github-lottery-reports). That second "notification" repository may be private, as it’s only about notifying maintainers.
Each maintainer who participates in the lottery (opt-in) gets their own dedicated GitHub issue in the "reports" repository, on which the application will add one comment mentioning the maintainer each time its sends a notification. That way, maintainers will get daily (or weekly) reports via email, sent by GitHub when the comment is added.
Issues/PRs are randomly assigned among eligible maintainers up to a limit they define themselves, so that everyone gets a chance to help according to the time they want to invest.
There are multiple categories of issues/PRs that one can be notified about; see Triagers/Maintainers/Stewards: how to get notifications for more information, but here’s what an email notification may look like:
As a Quarkus triager, a Quarkus core/extension maintainer, or a Quarkus steward, in order to get notifications about Quarkus issues/PRs on GitHub:
-
Make sure you have access to the "notification" repository if not, request access to an admin of the quarkusio organization.
-
Send a pull request to the "watched" repository (most likely https://github.com/quarkusio/quarkus) to edit file
.github/quarkus-github-lottery.yml. Add an entry with your username to theparticipantssection.
Here is what an entry will look like:
# [...]
participants:
- username: "yrodiere"
timezone: "Europe/Paris"
triage:
days: ["MONDAY", "WEDNESDAY", "FRIDAY"]
maxIssues: 3
maintenance:
labels: ["area/hibernate-orm", "area/hibernate-search"]
days: ["TUESDAY"]
feedback:
needed:
maxIssues: 4
provided:
maxIssues: 2
stale:
maxIssues: 5
stewardship:
days: ["MONDAY"]
maxIssues: 5username-
Your GitHub username.
String, mandatory, no default.
timezone-
Your timezone, to get notifications at the right time on the right day.
java.time.ZoneIdas a String, optional, defaults toUTC. triage-
Optional section for triagers.
See Triage for details.
maintenance-
Optional section for maintainers.
See Maintenance for details.
stewardship-
Optional section for stewards.
See Stewardship for details.
The triage, maintenance and stewardship sections are all optional;
you may participate in triage but not maintain an area of Quarkus nor do any stewardship, and vice-versa,
or do everything.
See below for details about each section.
If the triage section is present, you will get notified about Issues/PRs that haven’t been assigned an area yet.
Please add an area label, remove the "needs triage" (e.g. triage/needs-triage) label,
and ping the relevant maintainers if necessary.
Of course, some more discussion might be necessary before that, and that’s fine: issues that don’t change will reappear in another notification, a few days later.
The triage section will look like this:
# [...]
participants:
- username: "yrodiere"
triage:
days: ["MONDAY", "TUESDAY", "WEDNESDAY", "THURSDAY", "FRIDAY"]
maxIssues: 3days-
On which days you wish to get notified about triage.
Array of
WeekDays, mandatory, no default. maxIssues-
How many issues/PRs, at most, you wish to be included in the "triage" category for each notification.
Integer, mandatory, no default.
If the maintenance section is present, you will get notified about issues/PRs
related to a specific area (e.g. area/hibernate-orm)
that may be stalled and require intervention from maintainers or reporters.
Issues/PRs in "maintenance" notifications will be split in several categories:
- Created
-
Issues or PRs that just got created in your area.
Please review, ask for reproducer/information, or plan future work.
- Feedback Needed
-
Issues with missing reproducer/information.
Please ping the reporter, or close the issue if it’s taking too long.
- Feedback Provided
-
Issues with newly provided reproducer/information.
Please have a closer look, possibly remove the "needs feedback" (e.g.
triage/needs-reproducer) label, and plan further work. - Stale
-
Issues or PRs last updated a long time ago.
Please have a closer look, re-prioritize, ping someone, label as "on ice", close the issue/PR, …
Of course, in every situation, simply continuing the conversation, pinging someone, or even doing nothing at all are perfectly acceptable responses: it’s all up to you, and issues/PRs that don’t change will reappear in another notification, a few days later.
The maintenance section will look like this:
# [...]
participants:
- username: "yrodiere"
maintenance:
labels: ["area/hibernate-orm", "area/hibernate-search", "area/elasticsearch"]
days: ["MONDAY", "TUESDAY", "WEDNESDAY", "THURSDAY", "FRIDAY"]
created:
maxIssues: 5
feedback:
needed:
maxIssues: 4
provided:
maxIssues: 2
stale:
maxIssues: 5labels-
The labels identifying issues/PRs you are interested in, as a maintainer. Issues/PRs mentioned in notifications will have at least one of these labels.
Array of Strings, mandatory, no default.
days-
On which days you wish to get notified about maintenance.
Array of
WeekDays, mandatory, no default. created.maxIssues-
How many issues/PRs, at most, you wish to be included in the "Created" category for each notification.
Integer, mandatory if the
createdsection is present, no default. feedback.needed.maxIssues-
How many issues/PRs, at most, you wish to be included in the "Feedback needed" category for each notification.
Integer, mandatory if the
feedbacksection is present, no default. feedback.provided.maxIssues-
How many issues/PRs, at most, you wish to be included in the "Feedback provided" category for each notification.
Integer, mandatory if the
feedbacksection is present, no default. stale.maxIssues-
How many issues/PRs, at most, you wish to be included in the "Stale" category for each notification.
Integer, mandatory if the
stalesection is present, no default.
|
Important
|
This section should only be of interest to stewards: core contributors who spend significant time working on GitHub issues/PRs. If you don’t already know what this section is about, you probably don’t want to use it. |
If the stewardship section is present, you will get notified about issues or PRs across all areas last updated a long time ago.
Please have a closer look, re-prioritize, ping someone, label as "on ice", close the issue/PR, …
|
Note
|
Notifications to stewards are sent independently of notifications to maintainers, so that the work of maintainers won’t be affected by the work of stewards. It is entirely possible for a maintainer to be notified about an issue/PR at the same time as a steward. |
The stewardship section will look like this:
# [...]
participants:
- username: "yrodiere"
stewardship:
days: ["MONDAY"]
maxIssues: 5days-
On which days you wish to get notified about stewardship.
Array of
WeekDays, mandatory, no default. maxIssues-
How many issues/PRs, at most, you wish to be included in the "stewardship" category for each notification.
Integer, mandatory, no default.
Here is a link to the application on GitHub: https://github.com/apps/quarkus-github-lottery
The application needs to be installed on both the "source" repository (the one issues/PRs are extracted from) and the "notification" repository (the one "notification" issues are added to).
|
Important
|
For security reasons, the two GitHub repositories need to be in the same organization (technically, the same "installation"). Failing that, lottery draws will error out and will not send any notification. |
|
Tip
|
The "notification" repository should ideally be private:
|
The configuration file .github/quarkus-github-lottery.yml
includes several sections that are common to all participants to the lottery:
notifications:
createIssues:
repository: "quarkusio/quarkus-github-lottery-reports"
buckets:
triage:
label: "triage/needs-triage"
delay: PT0S
timeout: P3D
maintenance:
created:
delay: PT0S
timeout: P1D
expiry: P14D
ignoreLabels: ["triage/on-ice"]
feedback:
labels: ["triage/needs-reproducer"]
needed:
delay: P21D
timeout: P3D
provided:
delay: P7D
timeout: P3D
stale:
delay: P60D
timeout: P14D
ignoreLabels: ["triage/on-ice"]
stewardship:
delay: P60D
timeout: P14D
ignoreLabels: ["triage/on-ice"]
# [...]notifications.createIssues.repository-
The full name of the GitHub repository where "reports"/"notification issues" will be created.
String, mandatory, no default.
buckets.triage.label-
The label identifying GitHub issues/PRs that require triage.
String, mandatory, no default.
buckets.triage.delay-
How much time to wait after the last update on an issue/PR before including it in the lottery in the "triage" bucket.
String in ISO-8601 duration format, mandatory, no default.
buckets.triage.timeout-
How much time to wait after an issue/PR was last notified about before including it again in the lottery in the "triage" bucket.
String in ISO-8601 duration format, mandatory, no default.
buckets.maintenance.created.delay-
How much time to wait after the creation of an issue/PR before including it in the lottery in the "created" bucket.
String in ISO-8601 duration format, mandatory, no default.
buckets.maintenance.created.timeout-
How much time to wait after an issue/PR was last notified about before including it again in the lottery in the "created" bucket.
String in ISO-8601 duration format, mandatory, no default.
buckets.maintenance.created.expiry-
How much time to wait after the creation of an issue/PR before excluding it from the lottery in the "created" bucket.
String in ISO-8601 duration format, mandatory, no default.
buckets.maintenance.created.ignoreLabels-
The labels identifying GitHub issues/PRs that should be ignored for the "created" bucket. Issues/PRs with one of these labels will never be added to the bucket.
Array of Strings, optional, defaults to an empty array.
buckets.maintenance.feedback.labels-
The labels identifying GitHub issues for which feedback (a reproducer, more information, …) was requested.
Array of strings, mandatory, no default.
buckets.maintenance.feedback.needed.delay-
How much time to wait after the last update on an issue before including it in the lottery in the "feedback needed" bucket.
String in ISO-8601 duration format, mandatory, no default.
buckets.maintenance.feedback.needed.timeout-
How much time to wait after an issue was last notified about before including it again in the lottery in the "feedback needed" bucket.
String in ISO-8601 duration format, mandatory, no default.
buckets.maintenance.feedback.provided.delay-
How much time to wait after the last update on an issue before including it in the lottery in the "feedback provided" bucket.
String in ISO-8601 duration format, mandatory, no default.
buckets.maintenance.feedback.provided.timeout-
How much time to wait after an issue was last notified about before including it again in the lottery in the "feedback provided" bucket.
String in ISO-8601 duration format, mandatory, no default.
buckets.maintenance.stale.delay-
How much time to wait after the last update on an issue/PR before including it in the lottery in the "stale" bucket.
String in ISO-8601 duration format, mandatory, no default.
buckets.maintenance.stale.ignoreLabels-
The labels identifying GitHub issues/PRs that should be ignored for the "stale" bucket. Issues/PRs with one of these labels will never be added to the bucket.
Array of Strings, optional, defaults to an empty array.
buckets.maintenance.stale.timeout-
How much time to wait after an issue/PR was last notified about before including it again in the lottery in the "stale" bucket.
String in ISO-8601 duration format, mandatory, no default.
buckets.stewardship.delay-
How much time to wait after the last update on an issue/PR before including it in the lottery in the "stewardship" bucket.
String in ISO-8601 duration format, mandatory, no default.
buckets.stewardship.timeout-
How much time to wait after an issue/PR was last notified about before including it again in the lottery in the "stewardship" bucket.
String in ISO-8601 duration format, mandatory, no default.
buckets.stewardship.ignoreLabels-
The labels identifying GitHub issues/PRs that should be ignored for the "stewardship" bucket. Issues/PRs with one of these labels will never be added to the bucket.
Array of Strings, optional, defaults to an empty array.
The application will automatically add a check to any pull request that changes its configuration file.
The check is fairly simple, it just attempts to deserialize the YAML file and reports any exception.
Comment-based commands are available for admins. You can invoke it by adding a comment on any issue or pull request for repositories where the app is installed.
It supports the following commands:
-
/lottery draw: force a lottery draw immediately. Timeouts are still complied with, so this command is mostly useful if you manually edited the notification history or changed the configuration, which may happen frequently in dev mode in particular.
To participate in the development of this GitHub App, create a playground project in your own org and follow the steps outlined in the Quarkus GitHub App documentation.
When registering your app, request the following Repository permissions:
-
Checks -
Read & Write: to validate configuration files. -
Issues -
Read & Write: to list issues that should be notified, and to create "notification" issues in another repository. -
Pull Requests -
Read & Write: to list PRs that should be notified, and to react to comment-based commands.
And subscribe to the following events:
-
Check run, Check suite, Pull request: to validate configuration files.
-
Issue comment: to listen to comment-based commands.
Maintainers can review the application and update configuration/secrets on the OpenShift console.
There is only one namespace at the moment:
-
Production (
mainbranch):
Deployment will happen automatically when pushing to the relevant branch.
Be careful about which configuration you change in the UI, as deployment may overwrite part of the topology.