Error: PR does not contain metadata, nothing to do. about fetch-metadata HOT 4 CLOSED

The issue here is that if you use the commit-message.prefix value in the dependabot.yml it instantly becomes unparseable by this action, because this action parses the commit message as if it were never altered.

I was totally wrong. The issue is that the metadata isn't in the dependabot commit for it to be parsed back out.

Here is what a "good" commit looks like:

somewhatabstract/checksync@52e94cf

Bumps [rollup](https://github.com/rollup/rollup) from 2.57.0 to 2.58.0.
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/[email protected])

---
updated-dependencies:
- dependency-name: rollup
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

Note the updated-dependencies part. If that is absent, then this action cannot load the required metadata. My guess is that dependabot must've created the PRs in question BEFORE this metadata was getting added. I'll see if I can persuade my PRs to update with the metadata and get back to this issue.

from fetch-metadata.

I think this is a bug with dependabot. It seems that the inclusion of a prefix to the commit message is causing it to omit the metadata when creating the commit. :( It's because:

1. The commits were made by dependabot BEFORE it was adding metadata
2. @dependabot recreate doesn't actually recreate fully. It reuses the same commits and just rebases them - so it never updates them to add the metadata.

As far as I can tell, there's no easy way to convince it to do the right thing for these old PRs.

from fetch-metadata.

I agree with @somewhatabstract - this is caused by dependabot/dependabot-core#4652 and cannot be fixed in fetch-metadata

from fetch-metadata.

@Dreamsorcerer Unfortunately this isn't something we can fix in this project, @mwaddell is correct that we have a downstream issue in core to look at how we handle refreshing commit messages.

from fetch-metadata.