ci: add workflow to sync with upstream daily #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
This workflow runs the following steps daily: * Pull tags from upstream; * Rebase the default branch onto the latest tag for the current Fedora version; * Push the changes to the default branch, including tags. If the rebase encounters conflicts, the job will abort and conflicts will need to be resolved manually. Signed-off-by: Daniel Hast <hast.daniel@protonmail.com>
RoyalOughtness
approved these changes
Oct 3, 2025
github-actions bot
pushed a commit
that referenced
this pull request
Oct 4, 2025
This workflow runs the following steps daily: * Pull tags from upstream; * Rebase the default branch onto the latest tag for the current Fedora version; * Push the changes to the default branch, including tags. If the rebase encounters conflicts, the job will abort and conflicts will need to be resolved manually. Signed-off-by: Daniel Hast <hast.daniel@protonmail.com>
github-actions bot
pushed a commit
to HastD/secureblue-selinux-policy
that referenced
this pull request
Oct 6, 2025
This workflow runs the following steps daily: * Pull tags from upstream; * Rebase the default branch onto the latest tag for the current Fedora version; * Push the changes to the default branch, including tags. If the rebase encounters conflicts, the job will abort and conflicts will need to be resolved manually. Signed-off-by: Daniel Hast <hast.daniel@protonmail.com>
secureblue-bot
pushed a commit
that referenced
this pull request
Oct 6, 2025
This workflow runs the following steps daily: * Pull tags from upstream; * Rebase the default branch onto the latest tag for the current Fedora version; * Push the changes to the default branch, including tags. If the rebase encounters conflicts, the job will abort and conflicts will need to be resolved manually. Signed-off-by: Daniel Hast <hast.daniel@protonmail.com>
secureblue-bot
pushed a commit
that referenced
this pull request
Oct 15, 2025
This workflow runs the following steps daily: * Pull tags from upstream; * Rebase the default branch onto the latest tag for the current Fedora version; * Push the changes to the default branch, including tags. If the rebase encounters conflicts, the job will abort and conflicts will need to be resolved manually. Signed-off-by: Daniel Hast <hast.daniel@protonmail.com>
secureblue-bot
pushed a commit
that referenced
this pull request
Oct 26, 2025
This workflow runs the following steps daily: * Pull tags from upstream; * Rebase the default branch onto the latest tag for the current Fedora version; * Push the changes to the default branch, including tags. If the rebase encounters conflicts, the job will abort and conflicts will need to be resolved manually. Signed-off-by: Daniel Hast <hast.daniel@protonmail.com>
secureblue-bot
pushed a commit
that referenced
this pull request
Nov 14, 2025
This workflow runs the following steps daily: * Pull tags from upstream; * Rebase the default branch onto the latest tag for the current Fedora version; * Push the changes to the default branch, including tags. If the rebase encounters conflicts, the job will abort and conflicts will need to be resolved manually. Signed-off-by: Daniel Hast <hast.daniel@protonmail.com>
secureblue-bot
pushed a commit
that referenced
this pull request
Nov 20, 2025
This workflow runs the following steps daily: * Pull tags from upstream; * Rebase the default branch onto the latest tag for the current Fedora version; * Push the changes to the default branch, including tags. If the rebase encounters conflicts, the job will abort and conflicts will need to be resolved manually. Signed-off-by: Daniel Hast <hast.daniel@protonmail.com>
secureblue-bot
pushed a commit
that referenced
this pull request
Nov 27, 2025
This workflow runs the following steps daily: * Pull tags from upstream; * Rebase the default branch onto the latest tag for the current Fedora version; * Push the changes to the default branch, including tags. If the rebase encounters conflicts, the job will abort and conflicts will need to be resolved manually. Signed-off-by: Daniel Hast <hast.daniel@protonmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This workflow runs the following steps daily:
If the rebase encounters conflicts, the job will abort and conflicts will need to be resolved manually.