Move migration to end of tree

[norbye]

Description

Some migrations were added between making my previous PR and merging it, and I realized too late so here we are..

Testing

• The code quality is at a minimum required level of quality, readability, and performance.
• I have thoroughly tested my changes.

Please describe what and how the changes have been tested, and provide instructions to reproduce if necessary.

Resolves ... (either GitHub issue or Linear task)

[coderabbitai]

📝 Walkthrough

Walkthrough

The migration in the users application has been adjusted by updating its dependency. The file now relies on a different migration, which modifies the order in which the database schema changes are applied within the Django project.

Changes

File Path	Change Summary
lego/.../0048_alter_user_github_username_alter_user_linkedin_id.py	Updated migration dependency from ("users", "0045_user_achievement_score") to ("users", "0047_membershiphistory_users_membe_user_id_94537a_idx").

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4f034ed and 413366a.

📒 Files selected for processing (1)

• lego/apps/users/migrations/0048_alter_user_github_username_alter_user_linkedin_id.py (2 hunks)

🔇 Additional comments (1)

lego/apps/users/migrations/0048_alter_user_github_username_alter_user_linkedin_id.py (1)

11-12: Dependency updated correctly to maintain migration sequence.

The dependency has been correctly updated to point to the most recent migration (0047_membershiphistory_users_membe_user_id_94537a_idx) instead of the earlier 0045_user_achievement_score. This ensures that migrations are applied in the proper order, addressing the issue mentioned in the PR description about migrations that were added after the creation of a previous pull request.

🧰 Tools

🪛 Ruff (0.8.2)

11-13: Mutable class attributes should be annotated with typing.ClassVar

(RUF012)

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.