Skip to content

Dependabot on Actions page does not document Variables accessibility #43950

Closed

Description

@gokcedemir

Code of Conduct

What article on docs.github.com is affected?

What's wrong?

The Dependabot on GitHub Actions page lists restrictions when Dependabot triggers events, but does not mention anything about Actions Variables.

The current docs only say:

Secrets are populated from Dependabot secrets. GitHub Actions secrets are not available.

There is no mention of whether Actions Variables are accessible.

What should it say?

After testing, Actions Variables are accessible in Dependabot-triggered workflows. This should be documented.

Test repo: https://github.com/gokcedemir/dependabot-variables-test

Evidence

Workflow log shows:

  • Secret source: Dependabot (secrets come from Dependabot store)
  • TEST_VAR = hello_from_actions (Actions variable was accessible)

Related

What part(s) of the article would you like to see updated?

The "Restrictions when Dependabot triggers events" section should add a note that Actions Variables (vars context) ARE accessible in Dependabot-triggered workflows, unlike Actions Secrets which are not.

Suggested addition after the existing restrictions list:
"Actions variables (vars context) are accessible in workflows triggered by Dependabot."

Additional information

I tested this with a public repo: https://github.com/gokcedemir/dependabot-variables-test

The workflow log confirmed:

  • Secret source: Dependabot
  • vars.TEST_VAR was successfully accessed with its value

Screenshot of the log can be provided if needed.

Image

Activity

  1. added
    contentThis issue or pull request belongs to the Docs Content team
    on Apr 24, 2026
  2. welcome commented on Apr 24, 2026

    @welcome

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

  3. added
    triageDo not begin working on this issue until triaged by the team
    on Apr 24, 2026
  4. Zblumer1 commented on Apr 26, 2026

    @Zblumer1
  5. added
    dependabotContent related to Dependabot
    and removed
    triageDo not begin working on this issue until triaged by the team
    on Apr 28, 2026
  6. nsabedra27-glitch commented on May 3, 2026

    @nsabedra27-glitch
  7. nsabedra27-glitch commented on May 3, 2026

    @nsabedra27-glitch
  8. github-actions commented on Jun 22, 2026

    @github-actions
    Contributor

    A stale label has been added to this issue, because it has been open for 30 days with no activity. If you think this issue should remain open, please add a new comment.

  9. added
    InactiveWill be closed automatically by a stall check if no activity is detected.
    on Jun 22, 2026
  10. removed
    InactiveWill be closed automatically by a stall check if no activity is detected.
    on Jul 7, 2026
  11. github-actions commented on Aug 17, 2026

    @github-actions
    Contributor

    A stale label has been added to this issue, because it has been open for 30 days with no activity. If you think this issue should remain open, please add a new comment.

  12. added
    InactiveWill be closed automatically by a stall check if no activity is detected.
    on Aug 17, 2026
  13. removed
    InactiveWill be closed automatically by a stall check if no activity is detected.
    on Aug 17, 2026
  14. subatoi commented on Sep 10, 2026

    @subatoi
    Contributor

    Please see my comment here. Thank you very much

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    contentThis issue or pull request belongs to the Docs Content teamdependabotContent related to Dependabot

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions