ci: Add action to lint PR titles

[tushar-composio]

PR titles must follow conventional commits:

fix: Edge case in Outlook action
feat: New flow for OpenAPI spec uploads
chore: Bump version
ci: Update cache action to latest version

etc.

Important

Adds GitHub Action to validate pull request titles for semantic format using amannn/action-semantic-pull-request.

• CI/CD:
  • Adds .github/workflows/pr_title.yml to check PR titles for semantic format.
  • Triggers on opened, edited, synchronize, and reopened pull request events.
  • Uses amannn/action-semantic-pull-request@v5 to validate titles.
• Permissions:
  • Requires pull-requests: read permission.

^{This description was created by for 09a50ed. It will automatically update as commits are pushed.}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
composio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 6, 2024 6:45am

[ellipsis-dev]

❌ Changes requested. Reviewed everything up to 09a50ed in 35 seconds

More details

• Looked at 27 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 0 drafted comments based on config settings.

Workflow ID: wflow_pXvw8oxdnHcswjV4

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

Consider adding a configuration for the action-semantic-pull-request to specify the expected PR title format. This ensures the action checks against the desired title conventions.

[shreysingla11]

Consider adding configuration options for the semantic PR action to match the project's existing commit message standards. For example:

- uses: amannn/action-semantic-pull-request@v5
  with:
    # Define allowed types based on your development.md guidelines
    types: |
      feat
      fix
      docs
      test
    # Add a helpful error message
    errorComment: |
      Please follow the semantic PR title format as defined in python/docs/development.md

[shreysingla11]

Review Summary

Code Quality: 8/10

Positive Aspects:

• Well-structured GitHub Actions workflow
• Appropriate trigger events and minimal permissions
• Uses stable version (v5) of the semantic PR action
• Aligns with existing project standards documented in development.md

Suggestions for Improvement:

1. Add configuration options to match project's existing commit message standards
2. Consider adding helpful error messages for failed validations
3. Update development.md to reference this new automated check

The implementation is solid and will help enforce the project's existing semantic commit standards. The suggestions are mainly about improving user experience rather than fixing technical issues.

[github-actions]

This comment was generated by github-actions[bot]!

JS SDK Coverage Report

📊 Coverage report for JS SDK can be found at the following URL:
https://pub-92e668239ab84bfd80ee07d61e9d2f40.r2.dev/coverage-12194294039/coverage/index.html

📁 Test report folder can be found at the following URL:
https://pub-92e668239ab84bfd80ee07d61e9d2f40.r2.dev/html-report-12194294039/html-report/report.html