github: shallow-clone for actionlint and markdown check jobs

[ktdreyer]

For GitHub Actions that invoke setuptools-scm, we need the full Git history in order to get the proper versioning values from git describe (actions/checkout#249).

For GitHub Actions that do not invoke setuptools-scm, we do not need the full Git history, so we can speed up those clone operations with shallow clones.

Summary by Sourcery

CI:

• Remove full Git history fetch (fetch-depth: 0) from actionlint and markdown check jobs to improve clone performance

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request modifies the GitHub Actions workflows for actionlint and docs to remove the fetch-depth: 0 option from the checkout step. This ensures that the full Git history is available for these jobs, which is necessary for setuptools-scm to function correctly.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Removed the fetch-depth: 0 option from the actions/checkout step in the actionlint.yml workflow.	Removed fetch-depth: 0 from the checkout step.	.github/workflows/actionlint.yml
Removed the fetch-depth: 0 option from the actions/checkout step in the docs.yml workflow.	Removed fetch-depth: 0 from the checkout step.	.github/workflows/docs.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @ktdreyer - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider adding a comment to the workflow files explaining why fetch-depth: 0 was removed.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[ktdreyer]

(sourcery-ai's statement is misleading: This ensures that the full Git history is available for these jobs, which is necessary for setuptools-scm to function correctly. It's the other way around: we don't need full Git history on actionlint.yml and docs.yml.)

[abhi1092]

@ktdreyer thanks for the feedback on Sourcery. We are testing its effectiveness for PR review process.