8000 Use next_rails --init in docs by JuanVqz · Pull Request #143 · fastruby/next_rails · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Use next_rails --init in docs #143

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
Merged
merged 1 commit into from
Feb 26, 2025
Merged

Use next_rails --init in docs #143

merged 1 commit into from
Feb 26, 2025

Conversation

JuanVqz
Copy link
Member
@JuanVqz JuanVqz commented Feb 26, 2025

Description

Replace next --init with next_rails --init in the README.md

Motivation and Context

Since we are deprecating next --init, let's stop mentioning it in the
README.md

How Has This Been Tested?

It's just documentation change.

Screenshots:

I will abide by the code of conduct

@JuanVqz
Use next_rails --init in docs
71c120d 
Since we are deprecating `next --init`, let's stop mentioning it in the
README.md
@JuanVqz JuanVqz merged commit fa40882 into main Feb 26, 2025
8 checks passed
@JuanVqz JuanVqz deleted the update-next-init-readme branch February 26, 2025 14:22 675C
@eduardoj eduardoj mentioned this pull request Mar 31, 2025
Merged
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.
1 participant
@JuanVqz
0