Added Workflow for Sync in issue and PR #602

Adez017 · 2025-09-25T07:29:37Z

Description

This workflow synchronizes metadata from linked issues into the pull request body, including labels, assignees, and milestones.

Fixes #600

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

Added file for pr-issue-sync.yml

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.

This workflow synchronizes metadata from linked issues into the pull request body, including labels, assignees, and milestones.

vercel · 2025-09-25T07:29:42Z

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

A member of the Team first needs to authorize it.

github-actions · 2025-09-25T07:29:45Z

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 👇🏻

Get free Consultation use code recode50 to get free: Mentorship for free.
Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.
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! 😊

Copilot

Pull Request Overview

This PR introduces a GitHub workflow to automatically synchronize metadata (labels, assignees, and milestones) from linked issues into pull request descriptions. The workflow is triggered when PRs are opened, edited, or synchronized.

Key changes:

Added automated workflow to parse issue references in PR bodies
Implemented metadata extraction and synchronization from linked issues
Added PR body updates with formatted metadata blocks

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

Copilot · 2025-09-25T07:31:22Z

.github/workflows/pr-issue-sync.yml

+        uses: actions/github-script@v7
+        with:
+          script: |
+            const issues = JSON.parse(core.getInput("issues"));


The script attempts to read input 'issues' but it was set as an output in the previous step. This should be steps.extract.outputs.issues instead of core.getInput('issues').

Suggested change

const issues = JSON.parse(core.getInput("issues"));

const issues = JSON.parse(inputs.issues);

Copilot · 2025-09-25T07:31:22Z

.github/workflows/pr-issue-sync.yml

+            let newBody = pr.body || "";
+
+            // Remove old metadata block if exists
+            newBody = newBody.replace(/---\n###  Synced Metadata[\s\S]*$/, "");


The regex pattern searches for 'Synced Metadata' but the actual header being created is 'Synced data from Linked Issues' (line 67). This will result in duplicate metadata blocks being appended instead of replacing the existing one.

Suggested change

newBody = newBody.replace(/---\n### Synced Metadata[\s\S]*$/, "");

newBody = newBody.replace(/---\n### Synced data from Linked Issues[\s\S]*$/, "");

Copilot · 2025-09-25T07:31:23Z

.github/workflows/pr-issue-sync.yml

+
+            const metadataBlock =
+              `\n---\n` +
+              `###  Synced data from Linked Issues\n\n` +


There are extra spaces between '###' and 'Synced' which creates non-standard markdown formatting. This should be '### Synced data from Linked Issues' with a single space.

Adez017 · 2025-09-25T07:44:28Z

As the Forked doesn't have the permission it will fail here , to test the functionality we need to use hit and trial .

Copilot

Pull Request Overview

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

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

.github/workflows/pr-issue-sync.yml

Copilot · 2025-09-25T07:45:52Z

.github/workflows/pr-issue-sync.yml

+        uses: actions/github-script@v7
+        with:
+          script: |
+            const issuesInput = core.getInput("issues") || "[]";


The script tries to get input 'issues' but it should use the output from the previous step. Use steps.extract.outputs.issues instead of core.getInput('issues').

Suggested change

const issuesInput = core.getInput("issues") || "[]";

const issuesInput = process.env.ISSUES || "[]";

Copilot · 2025-09-25T07:45:52Z

.github/workflows/pr-issue-sync.yml

+        with:
+          script: |
+            const body = context.payload.pull_request.body || "";
+            const issuePattern = /#(\d+)/g;


The regex pattern will match any '#' followed by digits, potentially capturing false positives like '#123' in code snippets or unrelated contexts. Consider using a more specific pattern that looks for common issue linking phrases like 'fixes #123', 'closes #123', or 'resolves #123'.

Suggested change

const issuePattern = /#(\d+)/g;

const issuePattern = /\b(?:fixe?s|close[sd]?|resolve[sd]?)[:\s]+#(\d+)/gi;

vercel · 2025-09-25T10:24:08Z

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

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

sanjay-kv · 2025-09-25T10:25:26Z

secret with a PAT . have you used this @Adez017

Adez017 · 2025-09-25T15:16:29Z

secret with a PAT . have you used this @Adez017

No @sanjay-kv

Co-authored-by: Copilot <[email protected]>

Copilot

Pull Request Overview

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

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

Copilot · 2025-09-25T15:19:43Z

.github/workflows/pr-issue-sync.yml

+        uses: actions/github-script@v7
+        with:
+          script: |
+            const issuesInput = core.getInput("issues") || "[]";


The core.getInput("issues") call will not retrieve the output from the previous step. It should be steps.extract.outputs.issues to access the output from the extract step.

Suggested change

const issuesInput = core.getInput("issues") || "[]";

const issuesInput = steps.extract.outputs.issues || "[]";

Copilot · 2025-09-25T15:19:43Z

.github/workflows/pr-issue-sync.yml

+        with:
+          script: |
+            const body = context.payload.pull_request.body || "";
+            const issuePattern = /#(\d+)/g;


The regex pattern /#(\d+)/g will match any #number format, but GitHub's issue linking requires specific keywords like 'fixes', 'closes', 'resolves' followed by the issue number. This could incorrectly match unrelated hash numbers in the PR body.

Suggested change

const issuePattern = /#(\d+)/g;

// Match "fixes #123", "closes: #456", "resolves #789", etc. (case-insensitive)

const issuePattern = /\b(?:fixe?[sd]?|close[sd]?|resolve[sd]?)\s*[: ]+\s*#(\d+)/gi;

Adez017 · 2025-09-25T15:58:29Z

secret with a PAT . have you used this @Adez017

mail or anything else ?

sanjay-kv · 2025-09-26T00:06:44Z

No my qn was have you used PAT taken for this , if yes which one. Is it the one i sent you before via mail? @Adez017

Adez017 · 2025-09-26T04:18:18Z

No my qn was have you used PAT taken for this , if yes which one. Is it the one i sent you before via mail? @Adez017

No i directly used the secrets.GIT_TOKEN which is used in other workflows

Added Workflow for Sync in issue and PR

d927617

This workflow synchronizes metadata from linked issues into the pull request body, including labels, assignees, and milestones.

Copilot AI review requested due to automatic review settings September 25, 2025 07:29

Adez017 requested a review from iitzIrFan September 25, 2025 07:29

Copilot AI reviewed Sep 25, 2025

View reviewed changes

quick fix

2167ce9

Adez017 marked this pull request as draft September 25, 2025 07:36

Update PR issue sync workflow to use comments

53ea92a

Copilot AI review requested due to automatic review settings September 25, 2025 07:42

Adez017 marked this pull request as ready for review September 25, 2025 07:43

Copilot AI reviewed Sep 25, 2025

View reviewed changes

sanjay-kv approved these changes Sep 25, 2025

View reviewed changes

sanjay-kv assigned Adez017 Sep 25, 2025

sanjay-kv added gssoc25 level 2 30 points labels Sep 25, 2025

sanjay-kv added this to @recode-web Sep 25, 2025

sanjay-kv moved this to Todo in @recode-web Sep 25, 2025

sanjay-kv added this to the recode:launch 3.0 milestone Sep 25, 2025

vercel bot deployed to Preview September 25, 2025 10:25 View deployment

Update .github/workflows/pr-issue-sync.yml

71a2098

Co-authored-by: Copilot <[email protected]>

Copilot AI review requested due to automatic review settings September 25, 2025 15:18

Adez017 added the enhancement New feature or request label Sep 25, 2025

Copilot AI reviewed Sep 25, 2025

View reviewed changes

vercel bot deployed to Preview September 27, 2025 01:57 View deployment

sanjay-kv merged commit 57944ea into recodehive:main Sep 27, 2025
3 of 4 checks passed

github-project-automation bot moved this from Todo to Done in @recode-web Sep 27, 2025

	const issues = JSON.parse(core.getInput("issues"));
	const issues = JSON.parse(inputs.issues);

	newBody = newBody.replace(/---\n### Synced Metadata[\s\S]*$/, "");
	newBody = newBody.replace(/---\n### Synced data from Linked Issues[\s\S]*$/, "");

	const issuesInput = core.getInput("issues") \|\| "[]";
	const issuesInput = process.env.ISSUES \|\| "[]";

	const issuePattern = /#(\d+)/g;
	const issuePattern = /\b(?:fixe?s\|close[sd]?\|resolve[sd]?)[:\s]+#(\d+)/gi;

	const issuesInput = core.getInput("issues") \|\| "[]";
	const issuesInput = steps.extract.outputs.issues \|\| "[]";

	const issuePattern = /#(\d+)/g;
	// Match "fixes #123", "closes: #456", "resolves #789", etc. (case-insensitive)
	const issuePattern = /\b(?:fixe?[sd]?\|close[sd]?\|resolve[sd]?)\s[: ]+\s#(\d+)/gi;

Added Workflow for Sync in issue and PR #602

Added Workflow for Sync in issue and PR #602

Uh oh!

Conversation

Adez017 commented Sep 25, 2025

Description

Type of Change

Changes Made

Dependencies

Checklist

Uh oh!

vercel bot commented Sep 25, 2025

Uh oh!

github-actions bot commented Sep 25, 2025

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Uh oh!

Copilot AI Sep 25, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Sep 25, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Sep 25, 2025

Choose a reason for hiding this comment

Uh oh!

Adez017 commented Sep 25, 2025

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Uh oh!

Uh oh!

Copilot AI Sep 25, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Sep 25, 2025

Choose a reason for hiding this comment

Uh oh!

vercel bot commented Sep 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

sanjay-kv commented Sep 25, 2025

Uh oh!

Adez017 commented Sep 25, 2025

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Uh oh!

Copilot AI Sep 25, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Sep 25, 2025

Choose a reason for hiding this comment

Uh oh!

Adez017 commented Sep 25, 2025

Uh oh!

sanjay-kv commented Sep 26, 2025

Uh oh!

Adez017 commented Sep 26, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

vercel bot commented Sep 25, 2025 •

edited

Loading