Update GitHub language support article with footnotes and improved note formatting

[Copilot]

Fixes: https://github.com/github/docs-content/issues/14119

This PR makes several formatting improvements to the "GitHub language support" article:

Changes made

1. Added footnote references to PHP, Rust, and Scala entries in the core languages table
2. Reformatted the Note section below the table:
   • Removed bullet list formatting to make it a standard paragraph
   • Removed unnecessary bullets from all paragraphs
3. Moved the information about PHP, Rust, and Scala to a proper Markdown footnote at the bottom of the document
4. Enhanced the footnote text to clarify that these languages "are supported for code scanning by third-party actions, but not by {% data variables.product.prodname_codeql %}"

These changes improve readability while maintaining the proper relationship between the language entries in the table and their supporting information in the footnote.

Before and After

Before: The information about PHP, Rust, and Scala support was presented as a bulleted item in a note block.

After: This information is now properly linked as a footnote reference from each language name in the table, with the full explanation provided in a footnote at the bottom of the article.

This approach makes the relationship between the languages and the limitation more explicit, while keeping the main table clean and the note section focused on general information.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Pull Request Overview

This PR enhances the “GitHub language support” article by moving PHP, Rust, and Scala support notes into a footnote, cleaning up note formatting, and clarifying CodeQL limitations.

• Added [^1] footnote markers to PHP, Rust, and Scala entries
• Reformatted the NOTE block into plain paragraphs, removing list markers
• Introduced a Markdown footnote explaining third-party action support and CodeQL exclusion

Comments suppressed due to low confidence (1)

content/get-started/learning-about-github/github-language-support.md:45

• The blockquote marker (>) is placed after the Liquid tag, so it won’t render as a proper blockquote. Move the > to the start of the line, e.g., > {% ifversion fpt or ghec %} ....

{% ifversion fpt or ghec %}> The language support for {% data variables.product.prodname_copilot %} varies depending on the volume and diversity of training data for that language.{% endif %}

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
get-started/learning-about-github/github-language-support.md	fpt ghec ghes@ 3.17 3.16 3.15 3.14 3.13	fpt ghec ghes@ 3.17 3.16 3.15 3.14 3.13

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[hubwriter]

Copilot didn't realise the reusables were table rows, so you can't just stick a footnote superscript at the end of one. I've corrected this by putting the superscripts within the reusables.

Preview:

[Copilot]

Copilot didn't realise the reusables were table rows, so you can't just stick a footnote superscript at the end of one. I've corrected this by putting the superscripts within the reusables.

Preview...

Thanks for the correction! You're absolutely right - since the table uses reusable components, the footnote superscripts need to be placed within the reusables themselves rather than after the include statements. The fix in commit c3094d0 properly places the [^1] references in the "Code scanning" column within each reusable file.

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡