Skip to content

Run export for django 2.1 - #132

Merged
meshy merged 4 commits into
masterfrom
django-2.1
Jan 1, 2019
Merged

Run export for django 2.1#132
meshy merged 4 commits into
masterfrom
django-2.1

Conversation

@meshy

@meshy meshy commented Aug 21, 2018

Copy link
Copy Markdown
Contributor

Could someone load this fixture and sanity-check it for me?

Hopefully I'll be able to push this to the server in the morning.

@ghickman

Copy link
Copy Markdown
Contributor

@meshy – can you replace Opbeat with Sentry (in a seperate PR would be ace…)? I know Opbeat has gone away but it would be great to have Sentry in its place when we do a deploy!

@meshy

meshy commented Aug 22, 2018

Copy link
Copy Markdown
Contributor Author

Sounds like a good plan to me :)

@meshy meshy self-assigned this Aug 22, 2018
@meshy

meshy commented Sep 8, 2018

Copy link
Copy Markdown
Contributor Author

It's probably worth considering getting #135 sorted before continuing with this.

@meshy

meshy commented Jan 1, 2019

Copy link
Copy Markdown
Contributor Author

I've rebased this with a new dump based on the fixes from #135.

@meshy
meshy merged commit c675ea1 into master Jan 1, 2019
@meshy
meshy deleted the django-2.1 branch January 1, 2019 17:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants