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 linking to relevant tasks.
  • Added an automated labeling system for pull requests based on their size, enhancing organization and clarity.

• Documentation

  • New pull request template file created to standardize submissions.

• Chores

  • New GitHub Actions workflow for automatic pull request size labeling implemented.

[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 links to ClickUp tasks. The workflow automatically assigns labels to pull requests according to the number of lines changed, facilitating better organization and management of contributions.

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 GitHub Actions workflow to label pull requests based on their size, using defined thresholds.

Possibly related PRs

• feat: Add GitHub PR Checks Workflow #545: The main PR introduces a pull request template that includes a section for linking to ClickUp, which is directly related to the clickup_check introduced in the retrieved PR that requires PR descriptions to contain a ClickUp link.

🐇 In the garden, changes bloom,
A template crafted, dispelling gloom.
With labels bright, our PRs align,
ClickUp links, a task divine.
Hopping forward, we code with cheer,
Together we build, the future is near! 🌼

---

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
277	0 💤	0 ❌	0 🔥	38.846s ⏱️

[coderabbitai]

Actionable comments posted: 0

Outside diff range and nitpick comments (1)

.github/pull_request_template.md (1)

1-5: Enhance the pull request template by adding more sections.

The current template provides a good starting point by including sections for the PR description and the associated ClickUp task link. To capture more relevant information and provide better context for reviewers, consider adding the following sections:

1. Type of change: A section where the user can specify the type of change (feature, bug fix, refactor, etc.).
2. Testing instructions: A section where the user can provide instructions on how to test the changes.
3. Dependencies: A section where the user can list any dependencies or prerequisites for the changes.

Here's an example of how the enhanced template could look:

### Description
Please add PR description here, add screenshots if needed

### Type of change
- [ ] Feature
- [ ] Bug fix
- [ ] Refactor
- [ ] Other (please specify)

### Testing instructions
Please provide instructions on how to test the changes

### Dependencies
Please list any dependencies or prerequisites for the changes

## Clickup
Please add link here

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5fb7c92 and 8c6b7f4.

Files selected for processing (2)

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

Additional comments not posted (5)

.github/workflows/pr_size.yml (5)

1-3: LGTM!

The workflow name accurately describes its purpose, and triggering it on pull request events is appropriate for labeling PRs.

---

5-8: LGTM!

The job definition looks good. Using the latest version of Ubuntu ensures the workflow runs on a stable and up-to-date environment, and the job name accurately describes its purpose.

---

9-10: LGTM!

Using the pascalgn/size-label-action to label PRs based on size is a good choice. It's a well-maintained and popular action for this purpose. Pinning the action to a specific version ensures the workflow remains stable and reproducible.

---

11-12: LGTM!

Using the GITHUB_TOKEN secret to authenticate with the GitHub API is the recommended approach. The secret is correctly referenced using the secrets context.

---

13-21: LGTM!

The action configuration looks good. The size labels and their corresponding line change thresholds are defined in a clear and readable format. The chosen labels (XS, S, M, L, XL) are commonly used and easily understandable, and the thresholds seem reasonable for most projects.