jamesfredley commented on code in PR #14784: URL: https://github.com/apache/grails-core/pull/14784#discussion_r2133864741
########## .asf.yaml: ########## @@ -0,0 +1,29 @@ +# +# Licensed to the Apache Software Foundation (ASF) under one or more +# contributor license agreements. See the NOTICE file distributed with +# this work for additional information regarding copyright ownership. +# The ASF licenses this file to You under the Apache License, Version 2.0 +# (the "License"); you may not use this file except in compliance with +# the License. You may obtain a copy of the License at +# +# https://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. +# +# see https://s.apache.org/asfyaml + +notifications: + # GitHub related + commits: [email protected] + jobs: [email protected] + pullrequests_status: [email protected] + pullrequests_comment: [email protected] + pullrequests_bot_dependabot: [email protected] Review Comment: The volume statements were to gauge the level of activity that would end up in users@ and dev@, which we want to keep focused to user questions and development, respectively. After reviewing the volume, it changed my mind about adding PRs and Issues to dev@ or users@. For PRs notifications, I would be OK with `commits@` or `notifications@`, but was leaning slightly towards `commits@`, since PRs are closely related to the commits. Either way is fine. Groovy puts PRs in https://lists.apache.org/[email protected] - that would keep commits clean, as only commits. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
