#22511 closed Cleanup/optimization (fixed)
Usage help of makemigrations command missing argument for app
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Migrations | Version: | 1.7-beta-2 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The makemigrations command usage help shoud show:
Usage: manage.py makemigrations [options] [app_label]
Instead of:
Usage: manage.py makemigrations [options]
As pointed in documentation:
If your app already has models and database tables, and doesn’t have migrations yet (for example, you created it against a previous Django version), you’ll need to convert it to use migrations; this is a simple process:
$ python manage.py makemigrations your_app_label
Change History (5)
comment:1 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 12 years ago
| Has patch: | set |
|---|---|
| Resolution: | fixed |
| Status: | closed → new |
| Triage Stage: | Unreviewed → Accepted |
A ticket isn't marked fixed until it's committed, see triaging tickets.
comment:3 by , 12 years ago
I'm sorry, it's my first time contributing, I'll try to read more of the documentation on contributing before doing something else. Thanks!
comment:4 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Hi, I did a pull request to fix this ticket: https://github.com/django/django/pull/2606