create pr against sunshine

[ReenigneArcher]

Description

• create a pr against sunshine
  • This will update all ffmpeg submodules in a single PR, whereas dependabot creates a PR for every submodule branch, which generates a ton of workflow runs for Sunshine. This PR aims to reduce the workflow runs. Additionally it will be much faster to merge the changes into Sunshine as checks will only need to pass on a single PR instead of multiple.

📝 This depends on a fork of an action to enable PRs against another repository. Once this PR is merged, the workflow can be changed back to the original maintainer. repo-sync/pull-request#69

Todo:

• enable only on specific events (i.e. merge to master)
• enable job needs
• test that PR is created properly (should run immediately after creating this PR)
• specified PR labels are not added
• do not automerge these PRs -> add a way to not add autoapproved label based on title or body of PR .github#152

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[ReenigneArcher]

An issue was discovered.

The destination branch on sunshine still existed (although the previous PR was merged), and a new PR was created.

The destination branch looked like this when the PR was created.

Missing new commits from nightly.