assignUser commented on code in PR #41131: URL: https://github.com/apache/arrow/pull/41131#discussion_r1561896074
########## .github/workflows/release.yml: ########## @@ -0,0 +1,107 @@ +# 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: Release + +on: + push: + branches: + - "maint-[0-9]+.[0-9]+.[0-9]+" + - "release-[0-9]+.[0-9]+.[0-9]+" + - "release-[0-9]+.[0-9]+.[0-9]+-rc[0-9]+" + tags: + # Trigger workflow when a tag whose name matches either + # pattern "apache-arrow-{MAJOR}.{MINOR}.{PATCH}" or pattern + # "apache-arrow-{MAJOR}.{MINOR}.{PATCH}-rc{RC_NUM}" is pushed. + - "apache-arrow-[0-9]+.[0-9]+.[0-9]+" + - "apache-arrow-[0-9]+.[0-9]+.[0-9]+-rc[0-9]+" + +permissions: + contents: write + +env: + GH_TOKEN: ${{ github.token }} + +jobs: + publish: Review Comment: Having two jobs might be better after all, I thought we could join it in one job but the required steps are just slightly different enough that some degree of duplication makes it much easier to read (I can not read through this without forgetting which step applies when xD :see_no_evil: ). -- 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]
