-Request-context-property-similar-to-github-repository/m-p/38964/highlight/true#M3608
>
> No "include" like feature in GitHub Actions:
>
>
> https://github.community/t5/GitHub-Actions/Is-it-possible-to-reuse-workflow-yaml-to-setup-similar-workflows/m-p/40634#
>
>
ext-property-similar-to-github-repository/m-p/38964/highlight/true#M3608
No "include" like feature in GitHub Actions:
https://github.community/t5/GitHub-Actions/Is-it-possible-to-reuse-workflow-yaml-to-setup-similar-workflows/m-p/40634#
Thanks,
--
kou
In
"Re: [DISCUSS] Impr
On Tue, Feb 4, 2020 at 6:31 PM Wes McKinney wrote:
>
> I'm personally not too concerned with the details as long as people
> generally agree that the solution is maintainable (Kou's and Antoine's
> feedback here would be helpful) and there is not an abundant odor of
> code duplication
I'm not enti
I'm personally not too concerned with the details as long as people
generally agree that the solution is maintainable (Kou's and Antoine's
feedback here would be helpful) and there is not an abundant odor of
code duplication
On Tue, Feb 4, 2020 at 9:48 AM Neal Richardson
wrote:
>
> What if we wro
What if we wrote our own action(s) to wrap up some of the boilerplate? It
doesn't seem that there are any off-the-shelf actions we could use to drive
docker-compose:
https://github.com/marketplace?utf8=%E2%9C%93&type=actions&query=docker-compose
but I don't think it would be that difficult to wrap
Hi,
On Mon, Feb 3, 2020 at 5:25 PM Wes McKinney wrote:
>
> hi folks,
>
> I have noticed that many of our GitHub Actions configurations are very
> similar to each other
They are indeed.
>
> https://www.diffchecker.com/eF4tHdzo
>
> Aside from the "copy-paste" issue, some work would have to be done
hi folks,
I have noticed that many of our GitHub Actions configurations are very
similar to each other
https://www.diffchecker.com/eF4tHdzo
Aside from the "copy-paste" issue, some work would have to be done to
generate a Crossbow configuration using GHA.
It seems like a solution to these issues
