flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [flink] flinkbot commented on issue #9946: [FLINK-14468][docs] Update Kubernetes docs
Date Sun, 20 Oct 2019 13:33:13 GMT
flinkbot commented on issue #9946: [FLINK-14468][docs] Update Kubernetes docs
URL: https://github.com/apache/flink/pull/9946#issuecomment-544252792
 
 
   Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help
the community
   to review your pull request. We will use this comment to track the progress of the review.
   
   
   ## Automated Checks
   Last check on commit 43019ed32dab94129ea0a51d645f2dc55d18cd3d (Sun Oct 20 13:33:13 UTC
2019)
   
   **Warnings:**
    * Documentation files were touched, but no `.zh.md` files: Update Chinese documentation
or file Jira ticket.
    * **This pull request references an unassigned [Jira ticket](https://issues.apache.org/jira/browse/FLINK-14468).**
According to the [code contribution guide](https://flink.apache.org/contributing/contribute-code.html),
tickets need to be assigned before starting with the implementation work.
   
   
   <sub>Mention the bot in a comment to re-run the automated checks.</sub>
   ## Review Progress
   
   * ❓ 1. The [description] looks good.
   * ❓ 2. There is [consensus] that the contribution should go into to Flink.
   * ❓ 3. Needs [attention] from.
   * ❓ 4. The change fits into the overall [architecture].
   * ❓ 5. Overall code [quality] is good.
   
   Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html)
for a full explanation of the review process.<details>
    The Bot is tracking the review progress through labels. Labels are applied according to
the order of the review items. For consensus, approval by a Flink committer of PMC member
is required <summary>Bot commands</summary>
     The @flinkbot bot supports the following commands:
   
    - `@flinkbot approve description` to approve one or more aspects (aspects: `description`,
`consensus`, `architecture` and `quality`)
    - `@flinkbot approve all` to approve all aspects
    - `@flinkbot approve-until architecture` to approve everything until `architecture`
    - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention
    - `@flinkbot disapprove architecture` to remove an approval you gave earlier
   </details>

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message