-
Notifications
You must be signed in to change notification settings - Fork 111
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
enable preview for PRs? #297
Comments
that would be nice but never took the time to implement it |
tried to use netlify but so far failing in CI because of some bids schema version that is not PEP compliant (???) |
|
also struggling to set up the action you mentioned because of what seems to be a token access issue. see PR #301 |
Remi asked me for help on this, and I'll look into it soon (using the netlify preview, as for the bids-website repo) |
currently trying to get netlify going for this -- but I run into this during the build step of netlify:
and to be fair, the SCHEMA_VERSION does look uncompliant: feel free to check yourself: from pep440 import is_canonical
is_canonical('7.2.0-dev') # this will yield False Should we perhaps make the versioning system compliant with pep440? Something like cc @effigies EDIT: The funny thing is, that I cannot reproduce it locally. There, everything works as expected and without errors. |
Seems to not check out on Python 3.11, you mentioned in the meeting it failed on some part of the
Seems like it would be nice to be compliant with PEP 440, is this going to create issues with backwards compatibility? |
The ridiculous thing is that we specifically used something with a clear PEP440 normalization: https://peps.python.org/pep-0440/#development-release-separators |
Oh, this is weird. There haven't been any changes in the pep440 library since last year according to page on pypi so this has existed for quite a while. |
closing as this will probably be made obsolete by the merge of our websites. |
I guess would need smth like https://github.com/marketplace/actions/deploy-pr-preview . Inspired by inability to see the result in #294
The text was updated successfully, but these errors were encountered: