ASF GitHub Bot commented on FLINK-5751:

GitHub user uce opened a pull request:


    [FLINK-5751] [docs] Add link check script

    This is a slightly adjusted script from @patricklucas as posted in 
    I was wondering whether it makes sense to have it inside the repo, the 
local work flow would be:
    ./build_docs.sh -p
    You can overwrite the URL to check like `./check_links.sh 
    @rmetzger @patricklucas Should we include this?

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/uce/flink check_links

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3332
commit 50a879d8d18d009787fb6c67d78e0e5b79e010a9
Author: Ufuk Celebi <u...@apache.org>
Date:   2017-02-16T10:58:35Z

    [FLINK-5751] [docs] Add link check script


> 404 in documentation
> --------------------
>                 Key: FLINK-5751
>                 URL: https://issues.apache.org/jira/browse/FLINK-5751
>             Project: Flink
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Colin Breame
>            Priority: Trivial
>             Fix For: 1.3.0, 1.2.1
> This page:
> https://ci.apache.org/projects/flink/flink-docs-release-1.2/quickstart/setup_quickstart.html
> Contains a link with title "Flink on Windows" with URL:
> - 
> https://ci.apache.org/projects/flink/flink-docs-release-1.2/setup/flink_on_windows
> This gives a 404.  It should be:
> - 
> https://ci.apache.org/projects/flink/flink-docs-release-1.2/setup/flink_on_windows.html

This message was sent by Atlassian JIRA

Reply via email to