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.

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

Fix issue #901 by renaming database migrations to be snake cased #914

Merged
merged 1 commit into from
Jul 23, 2021
Merged

Fix issue #901 by renaming database migrations to be snake cased #914

merged 1 commit into from
Jul 23, 2021

Conversation

pacoorozco
Copy link
Contributor

Implement one of the options to fix #901. In this PR we rename database migrations to be snake cased.

I suggest this approach mainly for two reasons:

Signed-off-by: pacoorozco <paco@pacoorozco.info>
Copy link
Collaborator

@Gummibeer Gummibeer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your fix! 🎉

@Gummibeer Gummibeer merged commit 220a278 into spatie:master Jul 23, 2021
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.

Creating Migrations after vendor:publish
2 participants