This is an automated email from the ASF dual-hosted git repository.
ndimiduk pushed a change to branch 29787-addendum-master
in repository https://gitbox.apache.org/repos/asf/hbase.git
discard d33f2cc2e99 introduce some breakages
discard c5c565e5e0d cannot write comments from external fork PRs
discard ef64eb82ff5 override how generate the comment, only make links when we
have a url
discard e10add8f8d4 add support for line comments to our spotless extension
discard b1c1feaaec7 add a workflow to periodically hide old comments
discard 8cc3ca81c67 remove dependency on secrets
discard ca63fe1b177 HBASE-29787 Run Yetus General Checks as a GitHub Action
(addendum)
add 28dff30bdcd HBASE-29787 Run Yetus General Checks as a GitHub Action
(addendum)
add 751d6bf56bc pretty sure we're not using these permissions anymore
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (d33f2cc2e99)
\
N -- N -- N refs/heads/29787-addendum-master (751d6bf56bc)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.github/workflows/yetus-general-check.yml | 2 --
.../hadoop/hbase/testclassification/ClientTests.java | 20 ++++++++++++++++++--
2 files changed, 18 insertions(+), 4 deletions(-)
