From dev-return-74595-archive-asf-public=cust-asf.ponee.io@hbase.apache.org Thu Jun 6 16:14:05 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id B6B4318062B for ; Thu, 6 Jun 2019 18:14:04 +0200 (CEST) Received: (qmail 30574 invoked by uid 500); 6 Jun 2019 16:14:02 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 30506 invoked by uid 99); 6 Jun 2019 16:14:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Jun 2019 16:14:01 +0000 Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id CBEC3E2D30 for ; Thu, 6 Jun 2019 16:14:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 43FCA245CF for ; Thu, 6 Jun 2019 16:14:00 +0000 (UTC) Date: Thu, 6 Jun 2019 16:14:00 +0000 (UTC) From: "stack (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-22549) Document how to re-run github PR checks MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 stack created HBASE-22549: ----------------------------- Summary: Document how to re-run github PR checks Key: HBASE-22549 URL: https://issues.apache.org/jira/browse/HBASE-22549 Project: HBase Issue Type: Bug Components: documentation Reporter: stack Our [~psomogyi] has a trick for re-running github PR checks that is not force-push of original patch. Lets get it into the refguide. -- This message was sent by Atlassian JIRA (v7.6.3#76005)