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.

Sign up for GitHub

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

Jump to bottom

Clean up workflows #119

Merged
merged 6 commits into from
Feb 12, 2023
Merged

Clean up workflows #119

merged 6 commits into from
Feb 12, 2023

Commits on Feb 11, 2023

  1. chore: Add .gitignore

    @sondrelg
    sondrelg committed Feb 11, 2023
    Configuration menu
    Copy the full SHA
    7054f56 View commit details
    Browse the repository at this point in the history

  2. chore: Update pre-commit hooks

    @sondrelg
    sondrelg committed Feb 11, 2023
    Configuration menu
    Copy the full SHA
    c8868a5 View commit details
    Browse the repository at this point in the history

  3. chore: Delete poetry.lock 

    Since Poetry's lockfile formats aren't backwards compatible, we run into issues in our tests if we keep a v1.3.x version and vice versa for v1.2. This way each test can generate the format it needs.
    @sondrelg
    sondrelg committed Feb 11, 2023
    Configuration menu
    Copy the full SHA
    d07f64b View commit details
    Browse the repository at this point in the history

  4. chore: Update test-matrix versions

    @sondrelg
    sondrelg committed Feb 11, 2023
    Configuration menu
    Copy the full SHA
    af3f6e4 View commit details
    Browse the repository at this point in the history

  5. chore: Delete venv test 

    It's failing for some reason, and I can't figure out how this tests anything novel, so let's remove it.
    @sondrelg
    sondrelg committed Feb 11, 2023
    Configuration menu
    Copy the full SHA
    82dee43 View commit details
    Browse the repository at this point in the history

  6. chore: Remove old scripts 

    This might break a couple of workflows (hope not), but it's been 18 months since we changed the workflow to not rely on these, and the readme-examples have always used `v1`, so think the likelihood of things breaking for people is sufficiently low to finally go ahead with this.
    @sondrelg
    sondrelg committed Feb 11, 2023
    Configuration menu
    Copy the full SHA
    0453357 View commit details
    Browse the repository at this point in the history