Organization Variables that can include action runtime variables

[smithg6]

Body

I would like to see the ability to define an organization variable accessible by all org repos that would allow a team to migrate pipelines from sources like Azure DevOps, BitBucket, etc. to actions and workflows. This is currently limited by the exclusion of GITHUB_ as a valid variable value.

For example:

An in-house powershell module written for use in Azure Devops uses an available runtime variable like $BUILD_REPOSITORY_NAME in Azure Devops pipelines. There are dozens if not hundreds of places this reference is used in that code, and in order to maintain backwards compatibility in Azure Devops during the migration, we can't just update the module value easily which would create divergent modules and duplicate maintenance efforts.

One solution would be to setup any workflow using this module to have the following defined in the yaml

env:
    BUILD_REPOSITORY_NAME: ${{ github.repository }}

While this solution would work, it would also effectively duplicate that line into every single action template or workflow yaml needed across the 200 or so pipelines being rewritten.

What I am requesting is to be able to define an organization (or enterprise) variable that any actions or workflows running in that organization can evaluate based on how/where they are running. Not only for things like repository name, but for build ids, and other runner-available information.

BUILD_REPOSITORY_NAME = ${{ github.repository }}
or
BUILD_REPOSITORY_NAME = ${{ GITHUB_REPOSITORY }}

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐