Thanks to @udo and @nabarunnag the conversations and ideas around having
better review processes and review quality.
TL;DR - Adding GitHub CODEOWNERS[1] to geode-examples, eye toward adding to
GEODE
GitHub provides a mechanism of assigning code ownership to specific
owners/committers based on fil
Hi Robert,
Seems like a reasonable experiment. You can tag me if you like.
Thanks,
-Dan
From: Robert Houghton
Sent: Friday, October 30, 2020 1:52 PM
To: dev@geode.apache.org
Subject: Utilizing GitHub .CODEOWNERS files
Thanks to @udo and @nabarunnag the conversa
I'd be happy to volunteer as well
On 10/30/20, 2:10 PM, "Dan Smith" wrote:
Hi Robert,
Seems like a reasonable experiment. You can tag me if you like.
Thanks,
-Dan
From: Robert Houghton
Sent: Friday, October 30, 2020 1:52 PM
To:
Build Update for apache/geode-examples
-
Build: #469
Status: Errored
Duration: 21 secs
Commit: 3e22144 (rhoughton-pivot-patch-2)
Author: Robert Houghton
Message: ping pong - CODEOWNERS test
View the changeset: https://github.com/apache/geode-examples/commit/3e
Build Update for apache/geode-examples
-
Build: #471
Status: Errored
Duration: 21 secs
Commit: afb70bb (onichols-pivotal-patch-1)
Author: Owen Nichols
Message: Update build.gradle
this is bad, I hope someone catches it
View the changeset: https://github.com/a
