feat: change 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.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request makes minor changes to the PR validation workflow file, primarily focusing on whitespace adjustments and a slight modification to the semantic PR check condition.

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

File-Level Changes

Change	Details	Files
Whitespace adjustments in the PR validation workflow	Added extra blank lines after some job definitions Removed extra blank lines in other parts of the file Adjusted indentation in some areas	.github/workflows/pr_validation.yaml
Modified condition for semantic PR check	Changed the condition for running the semantic PR check from '

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#1	Add endpoints for file upload	❌	The PR does not implement any new endpoints. It only modifies a GitHub Actions workflow file.
#1	Add endpoints for file list	❌	The PR does not implement any new endpoints. It only modifies a GitHub Actions workflow file.
#1	Add endpoints for file delete	❌	The PR does not implement any new endpoints. It only modifies a GitHub Actions workflow file.
#2	Add a comprehensive README.md file	❌	The PR does not include any changes related to adding a README.md file. The changes are focused on modifying the PR validation workflow.
#2	Provide detailed documentation for the project	❌	The PR does not add any documentation. It only modifies the GitHub Actions workflow for PR validation.

---

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:

• The change in indentation for the 'semantic-pr' job condition might affect YAML parsing. Please verify that this modification doesn't alter the intended behavior of the workflow.
• The PR description lacks specific information about the changes made and their purpose. Please provide a clear explanation of the motivation behind these formatting adjustments and any potential benefits they bring to the workflow file.

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.}