kevinjqliu commented on code in PR #141: URL: https://github.com/apache/polaris/pull/141#discussion_r1726148135
########## .github/workflows/check-md-link.yml: ########## @@ -0,0 +1,43 @@ +# +# Copyright (c) 2024 Snowflake Computing Inc. +# +# Licensed under the Apache License, Version 2.0 (the "License"); +# you may not use this file except in compliance with the License. +# You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. +# + +# This workflow uses actions that are not certified by GitHub. +# They are provided by a third-party and are governed by +# separate terms of service, privacy policy, and support +# documentation. +# This workflow will find markdown links in the folder paths +# specified, and confirm the links are valid + +name: Check Markdown links + +on: + push: + paths: + - docs/** + - regtests/client/python/docs/** Review Comment: Looks like by default, not specifying the `folder-path` param will cause the action to look at all the MD files in the repo. https://github.com/gaurav-nelson/github-action-markdown-link-check?tab=readme-ov-file#custom-variables Maybe we can run this check for all MD files and for all PRs to cover all the edge cases. This way we don't need to allowlist new MD files not currently specified -- 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: dev-unsubscr...@polaris.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
