README update & removal of old CI configs - #1367
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Changes are limited to documentation/CI cleanup plus a least-privilege permissions adjustment that matches existing workflow patterns in the repo.
Review details
- Files reviewed: 4/4 changed files
- Comments generated: 0 new
- Review effort level: Lite
langou
approved these changes
Sep 8, 2026
Collaborator
Author
|
@langou Hi, it seems the AppVeyor webhook is still active and tries to build even after the config was removed. As a maintainer, you'll need to remove it, I think. It should be under Settings -> Webhooks. |
Contributor
|
Hi @ACSimon33, I just deleted the AppVeyor webhook. Cheers, Julien. |
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
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.
Description
As mentioned in #1363, the AppVeyor builds are now completely covered by the new GitHub Actions workflow. Since the AppVeyor builds are usually the bottleneck (single runner), I'd vote to remove them, alongside the old Travis config.
@langou If you think we should keep them or just turn off AppVeyor but keep the config, I'd be ok with that as well. If we want to remove them as this PR does, you probably have to remove the AppVeyor GitHub integration.
This PR also updates the badges in the README, and adds missing token permissions in the release.yml which should increase the OpenSSF Scodecard rating.