feat: changes in workflow

[psankhe28]

Description

• Fixes #(issue number)

Checklist

• My code follows the contributing guidelines
  of this project, including, in particular, with regard to any style guidelines
• The title of my PR complies with the
  Conventional Commits specification; in particular, it clearly
  indicates that a change is a breaking change
• I acknowledge that all my commits will be squashed into a single commit,
  using the PR title as the commit message
• I have performed a self-review of my own code
• I have commented my code in hard-to-understand areas
• I have updated the user-facing documentation to describe any new or
  changed behavior
• I have added type annotations for all function/class/method interfaces
  or updated existing ones (only for Python, TypeScript, etc.)
• I have provided appropriate documentation
  (Google-style Python docstrings) for all
  packages/modules/functions/classes/methods or updated existing ones
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature
  works
• New and existing unit tests pass locally with my changes
• I have not reduced the existing code coverage

Comments

Summary by Sourcery

Enhance the GitHub Actions workflow for pull request validation by expanding the event types that trigger the workflow and refining the conditions for semantic PR title checks.

CI:

• Update the GitHub Actions workflow to include additional pull request event types for triggering the workflow, such as 'synchronize', 'reopened', 'ready_for_review', and 'edited'.
• Ensure the semantic PR title check is only bypassed if the title has not been edited.

Summary by Sourcery

Enhance the GitHub Actions workflow for pull request validation by expanding the event types that trigger the workflow and refining the conditions for semantic PR title checks.

CI:

• Update the GitHub Actions workflow to include additional pull request event types for triggering the workflow, such as 'synchronize', 'reopened', 'ready_for_review', and 'edited'.
• Ensure the semantic PR title check is only bypassed if the title has not been edited.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request enhances the GitHub Actions workflow for pull request validation by expanding the event types that trigger the workflow and refining the conditions for semantic PR title checks. The changes focus on improving the CI process and updating the pre-commit checks.

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

File-Level Changes

Change	Details	Files
Update GitHub Actions workflow to include additional pull request event types	Add 'synchronize', 'reopened', 'ready_for_review', and 'edited' as trigger events for the workflow Ensure semantic PR title check is only bypassed if the title has not been edited	.github/workflows/pr_validation.yaml
Refactor pre-commit checks execution	Remove separate steps for installing and running pre-commit Replace pre-commit action with a direct command to run all pre-commit hooks	.github/workflows/pr_validation.yaml
Update job dependencies	Change 'needs: semantic-pr' to 'needs: semantic_pr' in the 'detect-unresolved-conflicts' job	.github/workflows/pr_validation.yaml

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#1	Add endpoints for file upload	❌	The PR does not implement any new endpoints. It focuses on changes to the GitHub Actions workflow.
#1	Add endpoints for file list	❌	The PR does not implement any new endpoints. It focuses on changes to the GitHub Actions workflow.
#1	Add endpoints for file delete	❌	The PR does not implement any new endpoints. It focuses on changes to the GitHub Actions workflow.
#2	Add a comprehensive README.md file	❌	The PR does not include any changes related to adding a README.md file. Instead, it focuses on changes to the GitHub Actions workflow.

---

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.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a 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. You can also use
  this command to specify where the summary should be inserted.

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 @psankhe28 - I've reviewed your changes - here's some feedback:

Overall Comments:

• Could you please explain the rationale behind removing the explicit pre-commit installation step? Have you ensured that pre-commit is available in the environment?
• We noticed several unchecked items in the PR checklist, particularly regarding tests and documentation. Could you address these points or explain why they're not applicable to this change?

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 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.}

[sourcery-ai]

issue (typo): Potential typo in job dependency name

The job dependency has been changed from 'semantic-pr' to 'semantic_pr'. This looks like it might be a typo, as the job is still named 'semantic-pr' later in the file. This could potentially break the workflow execution. Please verify if this change is intentional or if it needs to be corrected to maintain the proper job dependency.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (0b08ba9) to head (014832d).

Additional details and impacted files

@@            Coverage Diff            @@
##              main       #25   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines           30        30           
=========================================
  Hits            30        30           

Flag	Coverage Δ
test_integration	100.00% <ø> (ø)
test_unit	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.