Refine flatpak/dependabot conditions #9993
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
A while back in #9915 and #9930 we added some automation to keep the flatpak manifests in sync as dependabot tries to update the rust crates, and for the most part it has been working great! However, we find that after the job runs and commits the flatpak manifest, the job runs again and ends with an error because the new actor that did the commit doesn't have access to the dependabot secrets.
The error itself is harmless, but it means the CI is red and that makes me unhappy. So let's try to refine the workflow conditions a bit more so the job only runs once. To do this, we need to make it conditional on running with the dependabot actor too.
Reference
Introduced by #9915 and #9930
Checklist