fix: update broken git-workflow link in welcome message

[Suryas2125]

Description

• ...The problem: The "basic recommended setup" link in the welcome bot was returning a 404 because the file moved.
• ...The fix: Updated the URL to point to the new location in docs/010-contribution-guidelines/git-workflow.md.
• ...

Related issue(s)

Summary by CodeRabbit

• Chores

  • Enhanced first-time contributor welcome automation with improved validation and updated messaging for pull requests.

• Documentation

  • Updated contribution workflow documentation references in automated welcome messages.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[github-actions]

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated GitHub Actions workflow to enhance first-time contributor welcome messages. Changes include redirecting documentation references to a new path, introducing a pull request message constant, and adding validation to ensure messaging configuration is properly set.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow .github/workflows/welcome-first-time-contrib.yml	Updated issue message documentation path, introduced new prMessage constant for pull request messages, and added validation guard to ensure either issueMessage or prMessage is configured.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 The workflow hops with messages refined,
New paths and guards so well-designed!
First-time friends now find their way,
With validation checks leading the way! 🌟

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: updating a broken git-workflow link in the welcome message.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR fixes a broken link in the welcome message for first-time contributors. The "basic recommended setup" link was returning a 404 error because the git-workflow.md file was moved to a new location within the docs directory structure.

Changes:

• Updated the git-workflow.md link in the welcome message from community/blob/master/git-workflow.md to community/blob/master/docs/010-contribution-guidelines/git-workflow.md

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This file contains a warning at the top (lines 1-2) stating that it is "centrally managed in https://github.com/asyncapi/.github/" and changes made here "will be overwritten with changes made to the same file in above mentioned repo". This fix should likely be applied to the source file in the asyncapi/.github repository instead, otherwise it will be overwritten when the central repository syncs changes.

[Suryas2125]

Fixes #2264

[Varadraj75]

Hi @Suryas2125, thanks for working on this fix! I had reported this issue earlier and mentioned that I planned to work on it after maintainer confirmation. Just wanted to flag that for context and ensure we’re aligned with the contributing guidelines.

cc @derberg @AceTheCreator @thulieblack — would appreciate your guidance on how you’d like to proceed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[derberg]

Thanks for the contribution. I’m closing this PR because, while there is an existing issue, it was not approved or opened for contribution before the pull request was submitted.

Please make sure to follow the contribution guidelines, which explain when issues are considered ready for implementation and when pull requests are appropriate