Skip to content

Conversation

Adez017
Copy link
Member

@Adez017 Adez017 commented Sep 27, 2025

Description

Fixes #604

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

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 and devices
  • My changes do not generate new console warnings or errors .
  • I ran npm run build and attached screenshot(s) in this PR.
  • This is already assigned Issue to me, not an unassigned issue.

@Copilot Copilot AI review requested due to automatic review settings September 27, 2025 04:11
Copy link

vercel bot commented Sep 27, 2025

@Adez017 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! 😊

Copy link
Contributor

@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 automated labeling functionality for pull requests and issues, addressing issue #604. The implementation includes a new workflow to automatically apply standardized labels when PRs or issues are opened, and updates an existing workflow to improve data handling.

  • Introduces a new auto-labeling workflow that applies "recode" and "level 1" labels to newly opened PRs and issues
  • Updates the PR-issue sync workflow to use pull_request_target trigger and improve data extraction
  • Streamlines label management by automating the initial labeling process

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
.github/workflows/autolabler.yml New workflow for automatically adding standard labels to PRs and issues
.github/workflows/pr-issue-sync.yml Updated trigger and simplified data extraction logic

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

script: |
const issuesInput = core.getInput("issues") || "[]";
const issues = JSON.parse(issuesInput);
const issues = JSON.parse(`${{ steps.extract.outputs.issues }}`);
Copy link

Copilot AI Sep 27, 2025

Choose a reason for hiding this comment

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

Directly interpolating GitHub Actions output into JSON.parse() without proper escaping can lead to code injection vulnerabilities. Consider using fromJSON() function or proper input handling with core.getInput().

Suggested change
const issues = JSON.parse(`${{ steps.extract.outputs.issues }}`);
const issues = fromJSON(steps.extract.outputs.issues);

Copilot uses AI. Check for mistakes.

@Adez017
Copy link
Member Author

Adez017 commented Sep 27, 2025

Hi @sanjay-kv , i had made some changes in the sync file also for workflow , take a look on that one

@Adez017 Adez017 requested a review from sanjay-kv September 27, 2025 04:12
@Adez017 Adez017 added the don't-merge faced conflict issue or other dev related issue, dont merge PR label Sep 27, 2025
@Adez017
Copy link
Member Author

Adez017 commented Sep 27, 2025

@sanjay-kv , i think we need a PAT token for the actions with full permissions , is the current token has all ? i am refering to the PR i created yesterday .

@Adez017 Adez017 removed the don't-merge faced conflict issue or other dev related issue, dont merge PR label Sep 27, 2025
Copy link

vercel bot commented Sep 27, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
recode-website Ready Ready Preview Comment Sep 27, 2025 4:37am

@sanjay-kv sanjay-kv merged commit fcc04e3 into recodehive:main Sep 27, 2025
3 checks passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in @recode-web Sep 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Make autolabelling on issues and PR

2 participants