<blockquote>
<p>Yes we could do what you suggest and make travis constantly add new commits to bring the SQL back to a clean version but that will produce horrible churn in the git history unless we can somehow also prevent user changes making it through so that we only get the clean versions.</p>
</blockquote>
<p>Is it worth making a step in the travis to run the migrations, dump the structure, and fail the test run if the output is different from the committed structure? A little bit of <code>sed</code> before a <code>diff</code> could allow us to ignore the filesystem paths for the functions.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/issues/2211#issuecomment-486135333">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAK2OLMTH6A7DBPFES7KUALPSAPDTANCNFSM4HGGPRKA">mute the thread</a>.<img src="https://github.com/notifications/beacon/AAK2OLN2ZWRKO2PIPIA63FLPSAPDTANCNFSM4HGGPRKA.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/openstreetmap/openstreetmap-website","title":"openstreetmap/openstreetmap-website","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/openstreetmap/openstreetmap-website"}},"updates":{"snippets":[{"icon":"PERSON","message":"@gravitystorm in #2211: \u003e Yes we could do what you suggest and make travis constantly add new commits to bring the SQL back to a clean version but that will produce horrible churn in the git history unless we can somehow also prevent user changes making it through so that we only get the clean versions.\r\n\r\nIs it worth making a step in the travis to run the migrations, dump the structure, and fail the test run if the output is different from the committed structure? A little bit of `sed` before a `diff` could allow us to ignore the filesystem paths for the functions."}],"action":{"name":"View Issue","url":"https://github.com/openstreetmap/openstreetmap-website/issues/2211#issuecomment-486135333"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/openstreetmap/openstreetmap-website/issues/2211#issuecomment-486135333",
"url": "https://github.com/openstreetmap/openstreetmap-website/issues/2211#issuecomment-486135333",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>