You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Kevin Gurney (Jira)" <ji...@apache.org> on 2022/03/21 22:31:00 UTC
[jira] [Closed] (ARROW-15694) [Dev] Update apache/arrow-site GitHub Actions deploy.yml website deployment workflow to support being triggered when pushing to main
[ https://issues.apache.org/jira/browse/ARROW-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Gurney closed ARROW-15694.
--------------------------------
Merged via [https://github.com/apache/arrow-site/pull/202.]
> [Dev] Update apache/arrow-site GitHub Actions deploy.yml website deployment workflow to support being triggered when pushing to main
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ARROW-15694
> URL: https://issues.apache.org/jira/browse/ARROW-15694
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Developer Tools
> Reporter: Neal Richardson
> Assignee: Kevin Gurney
> Priority: Major
> Labels: pull-request-available
> Fix For: 8.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> As part of the transition away from using the name {{master}} for the default Git branch, we need to update the GitHub Actions website deployment workflow trigger.
> Since there does not appear to be any way to dynamically compute the default Git branch name in a GitHub Actions push trigger condition, a temporary workaround would be to add support for pushing to either {{master}} or {{{}main{}}}.
> Once Apache Infra switches the default Git branch for {{apache/arrow-site}} to {{{}main{}}}, we can completely remove support for triggering the GitHub Actions website deployment workflow on pushes to {{master}} from {{{}.github/workflows/deploy.yml{}}}. This follow up work is tracked by ARROW-15988.
> The main file that will need updating is {{{}.github/workflows/deploy.yml{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)