Hi Francis,
On Tue, Aug 27, 2019 at 12:19 PM Francis Chuang
wrote:
>
> I have implemented the ability to generate the website and javadoc for
> Calcite using Github Actions. See:
> https://github.com/apache/calcite/tree/test-site/.github/workflows
>
> The missing piece is that we need the token t
Hi Bertrand
On Tue, Aug 27, 2019 at 9:39 AM Bertrand Delacretaz
wrote:
>
> Hi,
>
> On Wed, Aug 7, 2019 at 1:33 PM Zoran Regvart wrote:
> >
> > ...for the Camel website we opted using docker containers with the
> > required tools instead of relying on the tools provided on the build
> > nodes
All,
The University is in the middle of doing a variety of power grid updates
[1] to campus which impact the building our datacenter is in (Kerr
Admin). *This
should not impact any production services since the data center will be on
generator power* however I like to notify everyone just in case
Hi Zoran,
I tired cloning from github.com, but pushing to it is still denied.
If I don't set any credentials in git, it complains that there is no
username for github.com:
https://github.com/apache/calcite/commit/d55e389310dcd024ae96623692a1e0a67274873c/checks
If I set the GITHUB_TOKEN as th
Hi Francis,
either that little loophole was closed or you're missing `user.email`
and `user.name` in your git config. Here's[1] how we used to do it for
the Camel website.
zoran
[1]
https://github.com/apache/camel-website/blob/master/.github/action-website/publish#L11-L12
On Thu, Sep 5, 2019 at
Many thanks for the example, Zoran.
I think I see the problem now. For camel-website you're running Github
actions in camel-website, so I think it implicitly allows you to push to
the same repo.
In my case, I have actions in calcite, calcite-avatica and
calcite-avatica-go pushing to calcite-
