Two migrations both depend on 0033_agentrun_agentstep:
0034_customuser_use_conversation_context
0034_waitlistentry
makemigrations reports multiple leaf nodes. Make one chain: 0033 → 0034_customuser_use_conversation_context → 0035_waitlistentry.
Do not drop the WaitlistEntry table or model. If 0034_waitlistentry is already recorded in django_migrations, the follow-up is to rename that row to 0035_waitlistentry before migrate.
Two migrations both depend on `0033_agentrun_agentstep`:
- `0034_customuser_use_conversation_context`
- `0034_waitlistentry`
`makemigrations` reports multiple leaf nodes. Make one chain: `0033` → `0034_customuser_use_conversation_context` → `0035_waitlistentry`.
Do not drop the WaitlistEntry table or model. If `0034_waitlistentry` is already recorded in `django_migrations`, the follow-up is to rename that row to `0035_waitlistentry` before migrate.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two migrations both depend on
0033_agentrun_agentstep:0034_customuser_use_conversation_context0034_waitlistentrymakemigrationsreports multiple leaf nodes. Make one chain:0033→0034_customuser_use_conversation_context→0035_waitlistentry.Do not drop the WaitlistEntry table or model. If
0034_waitlistentryis already recorded indjango_migrations, the follow-up is to rename that row to0035_waitlistentrybefore migrate.