feat: Enable PR lint workflow

[martimlobao]

• enable GH action for linting PRs
• check PR title follows Conventional Commits specification (https://www.conventionalcommits.org/)
• check yamllint and shellcheck
• use smaller screenshot in readme

Summary by Sourcery

Enable a GitHub Action workflow for linting pull requests, checking PR titles for compliance with the Conventional Commits specification, and running yamllint and shellcheck. Update the README to include a smaller screenshot.

CI:

• Introduce a GitHub Action workflow to lint pull requests, ensuring PR titles follow the Conventional Commits specification and running yamllint and shellcheck.

Documentation:

• Update README to use a smaller screenshot.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR adds a new GitHub Actions workflow for linting pull requests. The workflow performs three main checks: validates PR titles against Conventional Commits specification, runs shellcheck on shell scripts, and runs yamllint on YAML files. The workflow is triggered on pull request events including when PRs are opened, edited, synchronized, or reopened.

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

File-Level Changes

Change	Details	Files
Implementation of PR title validation workflow	Uses amannn/action-semantic-pull-request@v5 action to validate PR titles Configures workflow to trigger on pull_request_target events Sets minimal required permissions to read pull-requests	.github/workflows/lint_pr.yaml
Addition of shell script linting job	Implements shellcheck validation for all .sh files Uses -x flag to follow external sources Displays shellcheck version for debugging purposes	.github/workflows/lint_pr.yaml
Addition of YAML linting job	Implements yamllint validation for all YAML files Displays yamllint version for debugging purposes	.github/workflows/lint_pr.yaml

---

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

Overall Comments:

• Consider using pull_request instead of pull_request_target trigger unless you specifically need to access secrets in forked repo PRs
• The -x flag for shellcheck follows source statements which could be a security risk. Consider removing it unless absolutely necessary

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟡 Security: 1 issue found
• 🟢 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]

🚨 suggestion (security): Consider security implications of using pull_request_target

While pull_request_target is sometimes necessary for fork PR workflows, it runs with repository secrets and elevated permissions. Ensure this is required for your use case and consider using regular pull_request if possible.

Suggested change

	pull_request_target:
	pull_request: