kylerballiet opened a new pull request, #27746:
URL: https://github.com/apache/flink/pull/27746

   ## What is the purpose of the change
   
   Fix broken flink-training links in the Learn Flink docs. Several pages have 
a "Hands-on" section that use the `training_repo` and `training_link` 
shortcodes (e.g. Intro to the DataStream API, Data Pipelines & ETL, Streaming 
Analytics, Event-driven Applications). Two issues affected all of these: (1) 
the repo link pointed to a branch (e.g. release-2.2) that does not exist in 
apache/flink-training; (2) the exercise links used `blob` for paths that are 
directories in the repo, so the URLs were wrong. Both shortcodes now use the 
`master` branch, and the exercise shortcode uses `tree` instead of `blob`, so 
the links work on every page that uses them.
   
   ## Brief change log
   
     - `training_repo.html`: use `master` branch for the repo URL instead of 
`.Site.Params.Branch`
     - `training_link.html`: use `tree` instead of `blob` for exercise paths, 
and use `master` branch
   
   ## Verifying this change
   
   This change is a trivial rework / code cleanup without any test coverage.
   
   I built the docs locally using the project's pinned Hugo version (0.124.1 
via `setup_hugo.sh` and `build_docs.sh`) and verified the flink-training and 
exercise links on all affected Learn Flink pages (DataStream API, Data 
Pipelines & ETL, Streaming Analytics, Event-driven Applications); the links 
resolve correctly on each page. Note: building with a newer Hugo (e.g. 0.157 
from Homebrew) produced several unrelated template errors, so I used the pinned 
version for verification.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies: no
     - The public API: no
     - The serializers: no
     - The runtime per-record code paths: no
     - Anything that affects deployment or recovery: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to