Geethapranay1 opened a new pull request, #21831:
URL: https://github.com/apache/datafusion/pull/21831

   ## Which issue does this PR close?
   
   <!--
   We generally require a GitHub issue to be filed for all bug fixes and 
enhancements and this helps us generate change logs for our releases. You can 
link an issue to this PR using the GitHub syntax. For example `Closes #123` 
indicates that this PR will close issue #123.
   -->
   
   - Closes #21747 
   
   ## Rationale for this change
   datafusion did not have a CI check for broken links in markdown content, 
docs workflows build and deploy docs, and dev checks formatting and spelling, 
but none of them validate link targets.
   This pr adds a dedicated link check for internal markdown links so broken 
references fail early in PRs.
   I kept the scope internal-only to avoid flaky CI failures from external 
websites and rate limits.
   Rust doc comments remain covered by the existing rustdoc CI job.
   
   
   
   <!--
    Why are you proposing this change? If this is already explained clearly in 
the issue then this section is not needed.
    Explaining clearly why changes are proposed helps reviewers understand your 
changes and offer better suggestions for fixes.  
   -->
   
   ## What changes are included in this PR?
   
   
   - Added a new Dev workflow job, **Check Markdown Links**, in `dev.yml`.
   - Added `LYCHEE_VERSION` pin in `tool_versions.sh`.
   - Added `markdown_link_check.sh` to run lychee on the selected markdown 
paths.
   - Added `lychee.toml` with internal-link policy and exclusions.
   - Added check markdown links to required status checks in `.asf.yaml`.
   - Updated contributor testing docs with the new local command and scope note.
   - Fixed internal markdown links that failed under the new check in:
     - `roadmap.md`
     - `49.0.0.md`
     - `overview.md`
     - `dataframe.md`
     - `format_options.md`
   <!--
   There is no need to duplicate the description in the issue here but it is 
sometimes worth providing a summary of the individual changes in this PR.
   -->
   
   ## Are these changes tested?
   Yes,
   
   - `python3 ci/scripts/check_asf_yaml_status_checks.py` passed.
   - `bash -n ci/scripts/markdown_link_check.sh` passed.
   - `bash ci/scripts/markdown_link_check.sh` passed with 0 errors.
   - `cargo fmt --all --check` passed.
   
   OK: All 5 required_status_checks match existing GitHub Actions jobs.
   🔍 12824 Total (in 0s) ✅ 490 OK 🚫 0 Errors 👻 12334 Excluded
   <!--
   We typically require tests for all PRs in order to:
   1. Prevent the code from being accidentally broken by subsequent changes
   2. Serve as another way to document the expected behavior of the code
   
   If tests are not included in your PR, please explain why (for example, are 
they covered by existing tests)?
   -->
   
   ## Are there any user-facing changes?
   No,
   
   There is one contributor-facing CI change: PRs now fail when internal 
markdown links break in the checked markdown files.
   
   <!--
   If there are user-facing changes then we may require documentation to be 
updated before approving the PR.
   -->
   
   <!--
   If there are any breaking changes to public APIs, please add the `api 
change` label.
   -->
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to