docs: Fix broken community support link in issue template

[Skippou]

Description

This pull request fixes a broken link in the issue creation template (.github/ISSUE_TEMPLATE/config.yml). The "Community Support" contact link was pointing to https://github.com/google-health/langextract/discussions, which resulted in a 404 error for users trying to access the discussions page.

The link has been corrected to point to the correct discussions URL for the repository: https://github.com/google/langextract/discussions. Please note that this link will still result in a 404 error until the repository's "Discussions" tab is enabled by a maintainer.

Fixes #220

(Bug fix)

How Has This Been Tested?

I verified the fix by manually navigating to the corrected URL on a different repository (https://github.com/google/mangle/discussions) to ensure it leads to the correct page.

Since this is a simple URL change in a configuration file, no additional code tests were required.

Checklist:

-   [x] I have read and acknowledged Google's Open Source Code of conduct.
-   [x] I have read the Contributing page, and I either signed the Google Individual CLA or am covered by my company's Corporate CLA.
-   [x] I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach.
-   [x] I have made any needed documentation changes, or noted in the linked issue(s) that documentation elsewhere needs updating.
-   [ ] I have added tests, or I have ensured existing tests cover the changes
-   [x] I have followed Google's Python Style Guide and ran pylint over the affected code.

---

Note to maintainers: I noticed that the repository's "Discussions" tab is not yet enabled. Enabling it would make the "Community Support" link functional.

[github-actions]

❌ Infrastructure File Protection

This PR modifies protected infrastructure files:

• .github/ISSUE_TEMPLATE/config.yml (2 changes)

Only repository maintainers are allowed to modify infrastructure files (including .github/, build configuration, and repository documentation).

Note: If these are only formatting changes, please:

1. Revert changes to .github/ files
2. Use ./autoformat.sh to format only source code directories
3. Avoid running formatters on infrastructure files

If structural changes are necessary:

1. Open an issue describing the needed infrastructure changes
2. A maintainer will review and implement the changes if approved

For more information, see our Contributing Guidelines.

[github-actions]

⚠️ Branch Update Required

Your branch is 1 commits behind main. Please update your branch to ensure CI checks run with the latest code:

git fetch origin main
git merge origin/main
git push

Note: Enable "Allow edits by maintainers" to allow automatic updates.

[aksg87]

Thanks for the focused fix to the documentation! Please note, right now everything is flowing to issues but we can set up discussions soon. Will merge this for now as that will be the correct link when relevant.