danielcweeks commented on code in PR #4949: URL: https://github.com/apache/iceberg/pull/4949#discussion_r895072520
########## .github/workflows/stale.yml: ########## @@ -0,0 +1,48 @@ +# +# 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 +# +# http://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. +# + +name: "Close Stale Issues" +on: + schedule: + - cron: '0 0 * * *' + +permissions: + # All other permissions are set to none + issues: write + +jobs: + stale: + runs-on: ubuntu-20.04 + steps: + - uses: actions/stale@v4 + with: + stale-issue-label: 'stale' + exempt-issue-labels: 'not-stale' Review Comment: I think that behavior is largely covered, just in a slightly different way. The issue will be marked with the `stale` label after the period of inactivity and if anyone (author or otherwise) responds, the plugin will remove the `stale` label and the clock resets. We could change the label to be `awaiting reply` but I think that is less clear in this context than `stale`. We aren't specifically waiting for a reply and if you were to look at an issue with that label, it's wouldn't be as clear that it is considered stale. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
