docs: document that Actions variables are accessible in Dependabot workflows#43952
docs: document that Actions variables are accessible in Dependabot workflows#43952gokcedemir wants to merge 1 commit intogithub:mainfrom
Conversation
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
|
@gokcedemir Checking with the Dependabot team about this to make sure it's working as intended and that there's no reason we're not already documenting it. |
|
Actions variables should, as far as I'm aware, not be available to Dependabot. Even if they are available to the workflow (which I think would be an oversight?) they should not be accessible by the process that runs dependabot, because it runs in an isolated container. Let me look into this a bit please before publishing please |
Why:
Closes: #43950
What's being changed:
Added a bullet point to the "Restrictions when Dependabot triggers events" section documenting that Actions variables (
varscontext) are accessible in Dependabot-triggered workflows.Tested in: https://github.com/gokcedemir/dependabot-variables-test
Secret source: Dependabotvars.TEST_VARwas successfully accessed with its valueRelated community discussion: https://github.com/orgs/community/discussions/44088
Check off the following: