[
https://issues.apache.org/jira/browse/BEAM-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17259562#comment-17259562
]
Jarek Potiuk commented on BEAM-11569:
-------------------------------------
No problem. This approach (embedding the actions to your own repo) is also
good, it just makes it a bit more involved in case of new versions :)
BTW. For those kind of "embedding other repos", we've used and like a lot the
subrepo approach: [https://github.com/ingydotnet/git-subrepo] - it allows you
to embed other repo code in a subdirectory, but at the same time it keeps track
of the upstream versions and allows t both - update newer changes to the repo
as well as make PRs to the upstream from locally made changes.
> Github actions are failing on Beam repo
> ---------------------------------------
>
> Key: BEAM-11569
> URL: https://issues.apache.org/jira/browse/BEAM-11569
> Project: Beam
> Issue Type: Bug
> Components: testing
> Affects Versions: 2.27.0
> Reporter: Ahmet Altay
> Assignee: Pablo Estrada
> Priority: P0
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> As a result of https://issues.apache.org/jira/browse/INFRA-21234 github
> actions on Beam repo are failing.
> This is currently blocking 2.27.0 release because building wheel files depend
> on github actions. So far we identified 2 github actions that may need to be
> addressed:
> ad-m/github-push-action
> potiuk/cancel-workflow-runs
> Error looks like https://github.com/apache/beam/actions/runs/458287140
> """
> ad-m/github-push-action@master is not allowed to be used in apache/beam.
> Actions in this workflow must be: created by GitHub, verified in the GitHub
> Marketplace, within a repository owned by apache or match the following:
> apache/, gradle/wrapper-validation-action, gradle/wrapper-validation-action@,
> peter-evans/create-pull-request@, dawidd6/action-download-artifact@,
> scacap/action-surefire-report@*.
> """
> /cc [~potiuk] [~tysonjh]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
