chore: Added github action

[shubham-fyle]

https://app.clickup.com/t/86cwj8ynw

Summary by CodeRabbit

• New Features

  • Introduced a pull request template to guide contributors in providing detailed descriptions and relevant links.
  • Added an automated workflow for labeling pull requests based on their size, enhancing organization and clarity.

• Documentation

  • New pull request template file created to standardize submission details.

• Chores

  • Implemented a GitHub Actions workflow for automated pull request size labeling.

[coderabbitai]

Walkthrough

The changes introduce a new pull request template and a GitHub Actions workflow for labeling pull requests based on their size. The pull request template encourages contributors to provide detailed descriptions and relevant links. The workflow automates the labeling process using defined size thresholds, enhancing the management of pull requests by categorizing them according to their complexity.

Changes

File	Change Summary
.github/pull_request_template.md	Added a new pull request template with sections for description and ClickUp links.
.github/workflows/pr_size.yml	Introduced a new workflow for labeling pull requests by size using specified thresholds.

Poem

In the meadow where bunnies play,
A new template brightens the day.
With labels for sizes, neat and clear,
Pull requests now bring us cheer!
Hopping along, we code with glee,
Thanks to these changes, oh so free! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Tests	Skipped	Failures	Errors	Time
222	0 💤	0 ❌	0 🔥	24.345s ⏱️

[coderabbitai]

Actionable comments posted: 0

Outside diff range and nitpick comments (2)

.github/pull_request_template.md (1)

1-5: Consider enhancing the template with more details and sections.

To make the template more useful and informative, consider the following suggestions:

• Provide more guidance on what to include in the description section. For example, you could add a list of key points to cover, such as the problem statement, proposed solution, and potential impact.
• Clarify the purpose of linking the Clickup task and provide brief instructions on how to include the link. This will help contributors understand the context and ensure they provide the necessary information.
• Think about adding more sections to capture other important aspects of the pull request. Some ideas include:
  • Testing: Prompt the contributor to describe the testing steps performed and include any relevant test results or screenshots.
  • Deployment: Ask for any specific deployment instructions or considerations.
  • Rollback: Request information on how to roll back the changes if needed.
  • Checklist: Include a checklist of key items to review or verify before merging the PR.

By providing a more comprehensive template, you can streamline the PR review process and ensure that contributors provide all the necessary information upfront.

.github/workflows/pr_size.yml (1)

1-21: LGTM! The GitHub Actions workflow looks good.

The workflow is correctly defined to label the pull request based on the number of lines changed. It uses the pascalgn/size-label-action to automatically add size labels to the PR.

A few suggestions for potential improvements:

• Consider extending the workflow to add more jobs for other PR checks like linting, testing, etc.
• Adjust the sizes input based on your team's preferred PR size categorization. The current values are just an example, but you can modify them to suit your needs.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7970fde and abd300b.

Files selected for processing (2)

• .github/pull_request_template.md (1 hunks)
• .github/workflows/pr_size.yml (1 hunks)

Additional comments not posted (1)

.github/pull_request_template.md (1)

1-5: LGTM! The PR template provides a good starting point.

Adding a pull request template is a great way to standardize and guide contributors on providing relevant information. The current template includes prompts for a description and a Clickup link, which is a good start.