Feature Request: Include the workflow run that created/updated a pull request

Is there an existing issue for this?

• I have searched the existing issues

Feature description

When Dependabot creates or updates a pull request, include a reference to the originating workflow run directly in the pull request, either as a link in the PR description, a metadata field, or a comment.

Context

Today, dependabot runs exclusively through GitHub Actions. The workflow run that triggered a given PR is therefore known at creation time, yet that information is currently not surfaced anywhere in the pull request itself.

Benefits

1. Easier troubleshooting for non dependabot maintainers

Contributors often can't tell where a Dependabot PR came from or what triggered it. A direct link to the workflow run gives anyone the context they need to understand the PR's origin without dependencies for a Dependabot's maintainer.

2. Audit trail and compliance

Teams operating under compliance requirements benefit from being able to trace every PR back to a specific, automation event. This closes a gap in the chain of evidence between "dependency update was merged" and "here is the exact run that proposed it."

3. Faster debugging of unexpected changes

If a Dependabot PR contains surprising or seemingly incorrect changes, linking directly to the workflow run means maintainers can immediately inspect the logs, inputs, and environment that produced it rather than hunting through logs

4. Simplified recovery

When a Dependabot run only partially succeeds (some PRs opened, some not), knowing the exact run that was involved makes it far easier to identify what happened

Proposed Implementation

At minimum, include the workflow run URL as a line in the auto-generated PR description, e.g.:

Created by workflow run: https://<github host>/<owner>/<repo>/actions/runs/<run_id>

Who benefits

• Non-maintainer contributors trying to understand PR origins
• Security and compliance teams needing traceability
• Maintainers debugging partial or unexpected updates
• Any team running Dependabot at scale across many repositories

No file, test, or entry point is named in the issue. Start by locating the Dependabot GitHub Actions integration that creates or updates pull requests, then determine how the originating run URL can be retained; done means generated pull requests expose a usable link to that workflow run.