Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CI test against main of darkgraylib #598

Merged
merged 3 commits into from
Jan 7, 2025
Merged

Add CI test against main of darkgraylib #598

merged 3 commits into from
Jan 7, 2025

Conversation

akaihola
Copy link
Owner

@akaihola akaihola commented Jul 29, 2024

In test-future.yml, we already install Black, Flynt and isort from their main branch to get an ahead warning of any incompatibilities against their upcoming releases. Let's add our own Darkgraylib there as well.

@akaihola akaihola added the CI label Jul 29, 2024
@akaihola akaihola added this to the Darker 2.1.2 milestone Jul 29, 2024
@akaihola akaihola self-assigned this Jul 29, 2024
@akaihola akaihola force-pushed the future-own-libs branch 3 times, most recently from f8a6556 to 1a2b052 Compare January 2, 2025 22:04
@akaihola akaihola changed the title Add CI test against main of graylint and darkgraylib Add CI test against main of darkgraylib Jan 2, 2025
@akaihola akaihola force-pushed the future-own-libs branch 3 times, most recently from 357314d to 8f114c8 Compare January 3, 2025 16:59
The future compatibility test will now also update this package to the
tip of its `main` branch. This way we'll detect accidental
incompatibilities with our own library packages.
@akaihola akaihola merged commit 25d1f1b into master Jan 7, 2025
34 of 35 checks passed
@akaihola akaihola deleted the future-own-libs branch January 7, 2025 21:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging this pull request may close these issues.

2 participants