Skip to content

restore-file occasionally restores the wrong commit #4679

@fregante

Description

@fregante

Please ensure:

  • The bug is caused by Refined GitHub. It doesn't happen if I disable the extension.

Description

Rare occurrence but:

  1. Create X branch from main
  2. Force-push main to something else
  3. Create PR from branch X

Now you'll have a PR with the changes that the force-push made.

  1. Click "Restore file" on one of the files in the PR

You'll notice that the feature "succeeds" but the commits are empty. This is a live example: 419c37c (#4677)

Example URL

#4677, before it was rebased

Browser(s) used

Safari

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions