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

Passage à Django 3.2 #6217

Merged
merged 1 commit into from
Jan 22, 2022
Merged

Passage à Django 3.2 #6217

merged 1 commit into from
Jan 22, 2022

Conversation

Situphen
Copy link
Member

@Situphen Situphen commented Dec 27, 2021 •
edited
Loading

Passage à Django 3.2

Fixes #6008

QA :

  • source zdsenv/bin/activate && make update && make zmd-start && make run-back
  • Vérifier que le site web fonctionne globalement correctement

@Situphen Situphen added the C-Back Concerne le back-end Django label Dec 27, 2021
@Situphen Situphen mentioned this pull request Dec 27, 2021
Closed
@coveralls
Copy link

coveralls commented Dec 27, 2021 •
edited
Loading

Coverage Status

Coverage remained the same at 87.019% when pulling 3952bec on Situphen:django32 into 7be4440 on zestedesavoir:dev.

@Situphen Situphen mentioned this pull request Dec 27, 2021
Closed
@Situphen Situphen marked this pull request as ready for review December 27, 2021 14:16
@Situphen Situphen force-pushed the django32 branch 2 times, most recently from 4e76c60 to 67b4536 Compare December 27, 2021 21:18
artragis
artragis previously approved these changes Jan 22, 2022
View reviewed changes
@artragis artragis merged commit 18a1991 into zestedesavoir:dev Jan 22, 2022
@Situphen Situphen deleted the django32 branch January 22, 2022 12:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@artragis artragis artragis left review comments

Assignees
No one assigned
Labels
C-Back Concerne le back-end Django
Projects
Suivi des PR
Archived in project
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Points à investiguer pour le passage à Django 3.2
3 participants
@Situphen @coveralls @artragis