Fixes CI

[alvinunreal]

No description provided.

[claude]

Code Review for PR #5: Adding fetch-depth to checkout action

Summary

This PR adds fetch-depth: 0 to the checkout action in the awesome-lint workflow, which fetches the complete Git history instead of just the latest commit.

Code Quality & Best Practices ✅

• The change is minimal and follows proper YAML syntax
• Correctly indented and placed under the checkout action's with block
• Uses the appropriate configuration option for the actions/checkout@v4 action

Potential Issues & Considerations ⚠️

1. Performance Impact: Setting fetch-depth: 0 fetches the entire Git history, which can slow down the workflow for repositories with extensive history. For this awesome-list repository, the impact should be minimal.

2. Necessity: The change appears unmotivated - the workflow runs awesome-lint which typically only needs the current state of files. Consider if this is actually required for:

   • The awesome-lint tool itself
   • The markdown-link-check tool
   • Any future additions to the workflow

Security Concerns ✅

No security issues identified. The change only affects how much Git history is fetched during the workflow run.

Test Coverage 🔍

• This is a CI configuration change that doesn't require traditional test coverage
• The workflow will be tested on the next run after merge
• Consider running the workflow on this PR branch to verify it works as expected

Recommendations

1. Add context: Update the PR description to explain why full Git history is needed
2. Consider alternatives: If only recent history is needed, use a smaller fetch-depth value (e.g., fetch-depth: 10)
3. Documentation: Add a comment in the YAML file explaining why full history is required if this is indeed necessary

Verdict

The change is technically correct but lacks justification. Please provide context for why the full Git history is needed for this linting workflow.