workflows: periodically check for updates #139
Merged
Conversation
This file contains 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
probe() requires a cross-compiler with the win32 threading model, which effectively limits us to the builder container. Update checking doesn't need any of the configuration done by probe(), and it's convenient to run it outside the container. Signed-off-by: Benjamin Gilbert <[email protected]>
Automatically check for updates once a week, whenever wraps are updated, or on demand. Have openslide-bot maintain a PR with updates from wrapdb, and an issue for any remaining updates reported by `./build.sh updates`. We need to do this in the context of openslide-bot, rather than the GITHUB_TOKEN, because PRs created by the GITHUB_TOKEN can't put their head branch in a fork, and don't automatically run CI. However, we want to label the issues and PRs, which would require giving openslide-bot permissions on the repo. Instead, we have a second, privileged workflow to detect and label these issues/PRs. Since the workflow maintains the PR branch in openslide-bot's fork, which may have a stale main branch with different Actions workflows, the bot token must have the `workflow` scope to allow updating workflows in the branch. Workflows have been disabled in the fork to minimize the effects. Signed-off-by: Benjamin Gilbert <[email protected]>
DCO signed off ✔️All commits have been signed off. You have certified to the terms of the Developer Certificate of Origin, version 1.1. In particular, you certify that this contribution has not been developed using information obtained under a non-disclosure agreement or other license terms that forbid you from contributing it under the GNU Lesser General Public License, version 2.1. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Automatically check for updates once a week, whenever wraps are updated, or on demand. Have @openslide-bot maintain a PR with updates from wrapdb, and an issue for any remaining updates reported by
./build.sh updates.We need to do this in the context of @openslide-bot, rather than the
GITHUB_TOKEN, because PRs created by theGITHUB_TOKENcan't put their head branch in a fork, and don't automatically run CI. However, we want to label the issues and PRs, which would require giving @openslide-bot permissions on the repo. Instead, we have a second, privileged workflow to detect and label these issues/PRs.Since the workflow maintains the PR branch in @openslide-bot's fork, which may have a stale main branch with different Actions workflows, the bot token must have the
workflowscope to allow updating workflows in the branch. Workflows have been disabled in the fork to minimize the effects.To support this, allow the
./build.sh updatescommand to run without a suitable cross-compiler available.