modify the new-implementation.yml to trigger workflow on first PR

[nikhilkalburgi]

What kind of change does this PR introduce?

bugfix

Issue Number:

• Closes 🐛 Bug: Modify new-implementation.yml workflow to run only for first time contributors #755

Screenshots/videos:

If relevant, did you update the documentation?

No

Summary
This adds an additional condition to the existing check to trigger the action for first time contributors only for th path "data/tooling-data.yml"

Does this PR introduce a breaking change?

No

[github-actions]

Welcome to the JSON Schema Community. Thanks a lot for creating your first pull request!! 🎉🎉 We are so excited you are here! We hope this is only the first of many! For more details check out README.md file.

[DhairyaMajmudar]

Thank you @nikhilkalburgi for the PR can you pls. remove the yarn.lock file from the PR. This will fix the failing CI

[gregsdennis]

Why does this have so many changes?! Isn't this just a workflow edit?

[DhairyaMajmudar]

Why does this have so many changes?! Isn't this just a workflow edit?

The large diff is because of the changes done in yarn.lock file

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
website	✅ Ready (View Log)	Visit Preview	443551f

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (b8fa129) to head (dd91683).

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #938   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           10        10           
  Lines          373       373           
  Branches        94        94           
=========================================
  Hits           373       373           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[nikhilkalburgi]

Hi @DhairyaMajmudar @gregsdennis ,

I have updated this PR. Removed the changes that occured in yarn.lock file. Let me know, if the changes works for you.

[DhairyaMajmudar]

LGTM 🚀

[benjagm]

Hi @nikhilkalburgi Why you closed this PR?

[nikhilkalburgi]

Hi @benjagm ,

There was a small conflict in my forked repo, so re-forked the repo. I have created another PR #973 . Please refer to this new PR for implemented changes.