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

Test Django 3.0 & Python 3.8 on Travis #2441

Merged
merged 4 commits into from
Mar 1, 2020
Merged

Test Django 3.0 & Python 3.8 on Travis #2441

merged 4 commits into from
Mar 1, 2020

Conversation

browniebroke
Copy link
Contributor

@browniebroke browniebroke commented Jan 17, 2020 •
edited

Submitting Pull Requests

General

  • Make sure you use semantic commit messages.
    Examples: "fix(google): Fixed foobar bug", "feat(accounts): Added foobar feature".
  • All Python code must be 100% pep8 and isort clean.
  • JavaScript code should adhere to StandardJS.
  • If your changes are significant, please update ChangeLog.rst.
  • Feel free to add yourself to AUTHORS.

@browniebroke browniebroke changed the title Django 30 travis Test Django 3.0 & Python 3.8 on Travis Jan 17, 2020
@browniebroke browniebroke marked this pull request as ready for review January 17, 2020 16:34
@coveralls
Copy link

Coverage Status

Coverage remained the same at 94.439% when pulling 747590b on browniebroke:django-30-travis into 9e8e8b1 on pennersr:master.

@browniebroke browniebroke mentioned this pull request Feb 29, 2020
Closed
@browniebroke
Copy link
Contributor Author

I fixed the build by merging master into my branch. I think this is ready for review...

@pennersr pennersr merged commit 11444ff into pennersr:master Mar 1, 2020
@browniebroke browniebroke deleted the django-30-travis branch March 2, 2020 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@browniebroke @coveralls @pennersr