-
Notifications
You must be signed in to change notification settings - Fork 113
Added workflow for auto labels on PR and Issues #609
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@Adez017 is attempting to deploy a commit to the recode Team on Vercel. A member of the Team first needs to authorize it. |
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 👇🏻
If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊 |
There was a problem hiding this 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 }}`); |
Copilot
AI
Sep 27, 2025
There was a problem hiding this comment.
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()
.
const issues = JSON.parse(`${{ steps.extract.outputs.issues }}`); | |
const issues = fromJSON(steps.extract.outputs.issues); |
Copilot uses AI. Check for mistakes.
Hi @sanjay-kv , i had made some changes in the sync file also for workflow , take a look on that one |
@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 . |
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Description
Fixes #604
Type of Change
Changes Made
Dependencies
Checklist
npm run build
and attached screenshot(s) in this PR.