Remove beta note for Configuration variables

[adamchainz]

Why:

This beta note was out of date. It was added in 4717018 (Jan 2023) and the feature was announced as stable in July 2023.

c7404ec (Dec 2024) removed the beta note from “Defining configuration variables for multiple workflows”. This commit cleans up the last remaining usage, and the shared beta note file itself.

Closes: N/A

What's being changed (if available, include any code snippets, screenshots, or gifs):

As above, one note removed.

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[Copilot]

Pull Request Overview

This PR removes an outdated beta note about configuration variables now that the feature is generally available.

• Deleted the shared beta-note reusable file.
• Removed its inclusion in the “accessing contextual information” workflow docs.

Reviewed Changes

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

File	Description
data/reusables/actions/configuration-variables-beta-note.md	Removed obsolete beta note reusable
content/actions/writing-workflows/.../accessing-contextual-information-about-workflow-runs.md	Deleted reference to the removed beta-note reusable

Comments suppressed due to low confidence (1)

data/reusables/actions/configuration-variables-beta-note.md:1

• Verify that no other documentation pages reference this reusable to prevent broken include links.

-> [!NOTE]

[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
actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs.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.

[Sharra-writes]

@adamchainz Thanks for including all that information, made it easy to track down what I needed! I'll get this added to the merge queue once checks are passing.

[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 ⚡

[adamchainz]

Yay, thanks!