Rename Django's dev branch to main. #807
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
Codecov Report
@@ Coverage Diff @@
## master #807 +/- ##
=======================================
Coverage 97.47% 97.47%
=======================================
Files 18 18
Lines 992 992
Branches 151 151
=======================================
Hits 967 967
Misses 12 12
Partials 13 13 Continue to review full report at Codecov.
|
jezdez
commented
Mar 10, 2021
| @@ -5,19 +5,19 @@ on: [push, pull_request] | |||
| jobs: | |||
| build: | |||
| name: build (Python ${{ matrix.python-version }}, Django ${{ matrix.django-version }}) | |||
| runs-on: ubuntu-latest | |||
| runs-on: ubuntu-18.04 | |||
There was a problem hiding this comment.
This is basically to work around an issue with installing mysqlclient on Ubuntu 20.04 that I couldn't fix:
ImportError: libmysqlclient.so.20: cannot open shared object file: No such file or directory
There was a problem hiding this comment.
Hmm, I can look into this later.
ThePumpingLemma
approved these changes
Mar 10, 2021
tim-schilling
added a commit
to tim-schilling/django-simple-history
that referenced
this pull request
Aug 24, 2021
Coercing OneToOneFields to be ForeignKeys on historical models causes issues when the OneToOneField is a custom subclass that includes additional arguments that do not exist on the ForeignKey.__init__ method. These additional arguments can be specified via excluded_field_kwargs to allow these custom OneToOneFields be coerced into ForeignKeys on the historical model. Fixes jazzband#807
tim-schilling
added a commit
to tim-schilling/django-simple-history
that referenced
this pull request
Aug 24, 2021
Coercing OneToOneFields to be ForeignKeys on historical models causes issues when the OneToOneField is a custom subclass that includes additional arguments that do not exist on the ForeignKey.__init__ method. These additional arguments can be specified via excluded_field_kwargs to allow these custom OneToOneFields be coerced into ForeignKeys on the historical model. Fixes jazzband#807
tim-schilling
added a commit
to tim-schilling/django-simple-history
that referenced
this pull request
Aug 24, 2021
Coercing OneToOneFields to be ForeignKeys on historical models causes issues when the OneToOneField is a custom subclass that includes additional arguments that do not exist on the ForeignKey.__init__ method. These additional arguments can be specified via excluded_field_kwargs to allow these custom OneToOneFields be coerced into ForeignKeys on the historical model. Fixes jazzband#807
11 tasks
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.
More information: https://groups.google.com/g/django-developers/c/tctDuKUGosc/
Refs: django/django#14048