[
https://issues.apache.org/jira/browse/FINERACT-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17111921#comment-17111921
]
Michael Vorburger commented on FINERACT-970:
--------------------------------------------
Oups! Yeah, this is related - but it's not you doing something wrong... I'm
(very) surprised to see that (all of...) these GitHub Actions, apparently, run
on forks as well, not just the "main" repo (which I kind of assumed and would
find more logical). I need to investigate ASAP (this weekend, not now) how to
restrict GitHub Actions to not run on any works... unless you want to dig into
that a bit? There's presumably some.... configuration know / flag / something
one can (hopefully) set in the YAMLs?
> Automatically continuously integrate and deploy ("CI/CD") Fineract develop
> branch to fineract.dev
> -------------------------------------------------------------------------------------------------
>
> Key: FINERACT-970
> URL: https://issues.apache.org/jira/browse/FINERACT-970
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Michael Vorburger
> Assignee: Michael Vorburger
> Priority: Major
> Fix For: 1.4.0
>
>
> The goal of this issue is to have every pull request merged to the develop
> branch on https://github.com/apache/fineract/ be as quickly as possible
> automatically continuously built and deployed ("CI/CD") to (my)
> https://www.fineract.dev demo server.
> I originally requested INFRA-20143 for this, but meanwhile found a better
> way. Given that we're in in 2020 not 1990, I was surprised how non-trivial is
> is to do this in an open yet secure way... I think I'll write up a short
> personal blog post about it when I'm fully done with this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
