Skip to content

WIP linkspector update #179

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

djmaxus
Copy link
Owner

@djmaxus djmaxus commented Jun 19, 2025

closes #178

@Copilot Copilot AI review requested due to automatic review settings June 19, 2025 21:20
@djmaxus djmaxus linked an issue Jun 19, 2025 that may be closed by this pull request
@djmaxus djmaxus self-assigned this Jun 19, 2025
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds a configuration file for linkspector and updates the GitHub Actions workflow to use it and fix the token name.

  • Introduces .linkspector.yml to explicitly include/exclude files and respect .gitignore.
  • Updates the links workflow to use the correct GITHUB_TOKEN, uncomments level: info, and points to the new config file.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
.linkspector.yml New linkspector config listing files to check and exclusions.
.github/workflows/links.yml Fixed token secret casing, enabled level, and added config_file setting.
Comments suppressed due to low confidence (3)

.linkspector.yml:6

  • [nitpick] Remove or replace this commented placeholder if you don't need directory-level includes. Leaving unused commented keys can confuse future maintainers.
# dirs:

.linkspector.yml:9

  • [nitpick] Either define which directories to exclude or remove this commented line to keep the config concise and clear.
# excludedDirs:

.github/workflows/links.yml:16

  • Consider pinning to a more specific version (e.g., @v1.2.3) instead of @v1 to avoid unexpected changes if the action's major version rolls forward.
        uses: umbrelladocs/action-linkspector@v1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix Linkspector's performance and reliability
1 participant