Skip to content

Conversation

iitzIrFan
Copy link
Member

Description

Provide a brief summary of the changes made to the website and the motivation behind them. Include any relevant issues or tickets.
This helps fast tracking your PR and merge it, Check the respective box below.

Fixes # (issue)

Type of Change

  • New feature (e.g., new page, component, or functionality)
  • Bug fix (non-breaking change that fixes an issue)
  • UI/UX improvement (design, layout, or styling updates)
  • Performance optimization (e.g., code splitting, caching)
  • Documentation update (README, contribution guidelines, etc.)
  • Other (please specify):

Changes Made

  • Describe the key changes (e.g., new sections, updated components, responsive fixes).

Dependencies

  • List any new dependencies or tools required for this change.
  • Mention any version updates or configurations that need to be considered.

Checklist

  • My code follows the style guidelines of this project.
  • I have tested my changes across major browsers/devices
  • My changes do not generate new console warnings or errors , I ran npm run build and attached scrrenshot in this PR.
  • This is already assigned Issue to me, not an unassigned issue.

Copy link

vercel bot commented Aug 21, 2025

Someone is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs.

In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Your perks for contribution to this community 👇🏻

  1. Get free Consultation use code recode50 to get free: Mentorship for free.

  2. Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.

  3. Check out this weekly Newsletter: Sanjay's Newsletter.

If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

@iitzIrFan iitzIrFan requested a review from Copilot August 21, 2025 10:33
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds a GitHub Actions workflow to automatically assign reviewers and assignees to issues and pull requests when they are opened, edited, or have labels changed.

  • Creates an auto-assignment workflow that triggers on issue and PR events
  • Configures specific users as default reviewers and assignees
  • Implements skip logic for items marked as work-in-progress or draft

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

run:
runs-on: ubuntu-latest
steps:
- uses: wow-actions/auto-assign@v3
Copy link
Preview

Copilot AI Aug 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using a third-party action without pinning to a specific commit hash can introduce security vulnerabilities if the action is compromised. Consider pinning to a specific commit hash instead of using a tag (e.g., 'wow-actions/auto-assign@abc123...').

Suggested change
- uses: wow-actions/auto-assign@v3
- uses: wow-actions/auto-assign@b7e6e2e2e2e2e2e2e2e2e2e2e2e2e2e2e2e2e2e2

Copilot uses AI. Check for mistakes.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sanjay-kv Need your review here.

Change as can cause security issues later

Co-authored-by: Copilot <[email protected]>
@iitzIrFan iitzIrFan requested a review from sanjay-kv August 21, 2025 19:32
@iitzIrFan iitzIrFan moved this to In Progress in @recode-web Aug 21, 2025
@sanjay-kv sanjay-kv added the prioriy:low Bug with a simple workaround that would not block a release label Aug 22, 2025
@sanjay-kv sanjay-kv added this to the recode:launch 3.0 milestone Aug 22, 2025
@iitzIrFan iitzIrFan added the Ready for Merge PR has passed reviews and checks, and is ready to be merged into the main branch. label Aug 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prioriy:low Bug with a simple workaround that would not block a release Ready for Merge PR has passed reviews and checks, and is ready to be merged into the main branch.
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

2 participants