Apache
/
druid
mirror of https://github.com/apache/druid.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
druid/.asf.yaml

35 lines
1.6 KiB
YAML
Raw Normal View History

Update .asf.yaml to simplify email subjects. (#14494) Currently, github notification emails to commits@druid.apache.org have a wide variety of subject lines. This foils email client threading and makes the firehose of emails hard to follow. This is an attempt, inspired by the config for plc4x, to make the emails easier to follow. After this change, it may even make sense to send some to dev@ instead of commits@.
2023-06-28 13:56:38 -04:00
# note: documentation can be found here https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features
Add .asf.yaml. (#9083) Based on the docs at https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories.
2019-12-20 19:45:38 -05:00
github:
description: 'Apache Druid: a high performance real-time analytics database.'
homepage: https://druid.apache.org/
Update .asf.yaml to simplify email subjects. (#14494) Currently, github notification emails to commits@druid.apache.org have a wide variety of subject lines. This foils email client threading and makes the firehose of emails hard to follow. This is an attempt, inspired by the config for plc4x, to make the emails easier to follow. After this change, it may even make sense to send some to dev@ instead of commits@.
2023-06-28 13:56:38 -04:00
# Attempt to make the auto-generated github emails more easily readable in email clients.
# Configuration adapted from https://github.com/apache/plc4x/blob/develop/.asf.yaml.
custom_subjects:
.asf.yaml: Add required "repository" field. (#14499) Our new .asf.yaml is not getting picked up because custom_subjects must include "repository".
2023-06-28 18:05:07 -04:00
new_pr: "[PR] {title} ({repository})"
close_pr: "Re: [PR] {title} ({repository})"
comment_pr: "Re: [PR] {title} ({repository})"
diffcomment: "Re: [PR] {title} ({repository})"
merge_pr: "Re: [PR] {title} ({repository})"
new_issue: "[I] {title} ({repository})"
comment_issue: "Re: [I] {title} ({repository})"
close_issue: "Re: [I] {title} ({repository})"
catchall: "[GH] {title} ({repository})"
new_discussion: "[D] {title} ({repository})"
edit_discussion: "Re: [D] {title} ({repository})"
close_discussion: "Re: [D] {title} ({repository})"
close_discussion_with_comment: "Re: [D] {title} ({repository})"
reopen_discussion: "Re: [D] {title} ({repository})"
new_comment_discussion: "Re: [D] {title} ({repository})"
edit_comment_discussion: "Re: [D] {title} ({repository})"
delete_comment_discussion: "Re: [D] {title} ({repository})"
Update .asf.yaml to simplify email subjects. (#14494) Currently, github notification emails to commits@druid.apache.org have a wide variety of subject lines. This foils email client threading and makes the firehose of emails hard to follow. This is an attempt, inspired by the config for plc4x, to make the emails easier to follow. After this change, it may even make sense to send some to dev@ instead of commits@.
2023-06-28 13:56:38 -04:00
notifications:
commits: commits@druid.apache.org
issues: commits@druid.apache.org
discussions: commits@druid.apache.org
pullrequests_status: commits@druid.apache.org
pullrequests_comment: commits@druid.apache.org
pullrequests_bot_dependabot: commits@druid.apache.org