Reranko05 commented on code in PR #55352: URL: https://github.com/apache/arrow/pull/55352#discussion_r4435911218
########## .github/workflows/unassign_bot.js: ########## @@ -0,0 +1,340 @@ +// 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. + +// Releases abandoned assignments on newcomer-friendly issues: +// - a linked PR is closed without merging and no other open linked PR +// exists from the same author -> unassign immediately +// - no qualifying activity for WARN_AFTER_DAYS -> warn, +// then unassign GRACE_DAYS later if there is still no activity. + +const helpers = require("./dev_pr/helpers.js"); + +const WARN_AFTER_DAYS = 5; +const GRACE_DAYS = 3; Review Comment: I also came across the [documentation](https://github.com/apache/arrow/blob/main/docs/source/developers/guide/step_by_step/finding_issues.rst#github-labels) stating that good-first-issues should take no more than two days or a weekend to solve: > The issues labeled as good first issues should take no more than two days or a weekend to fix them. That's another reason I felt that 30 days might be unnecessarily long for these issues. My intention was to give contributors enough time to make progress while still keeping these issues available for others if they become inactive. -- 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]
