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

Seed data #8

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Seed data #8

wants to merge 4 commits into from

Conversation

tqt97
Copy link
Owner

@tqt97 tqt97 commented Feb 18, 2024

No description provided.

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

PR Type: Unknown

PR Summary: The pull request titled 'Seed data' lacks a diff, making it impossible to assess the scope, intent, and impact of the proposed changes. Without any code changes to review, the purpose and content of the PR remain unclear.

Decision: Comment

📝 Type: 'Unknown' - not supported yet.
  • Sourcery currently only approves 'Typo fix' PRs.
📝 Issue not addressed: this change does not correctly address the issue or implement the desired feature.
No details provided.
📝 Complexity: the changes are too large or complex for Sourcery to approve.
  • Unsupported files: the diff contains files that Sourcery does not currently support during reviews.

General suggestions:

  • Ensure that the PR includes a diff of the proposed changes. This is crucial for reviewers to understand what modifications are being made and to provide meaningful feedback.
  • Clarify the intent of the PR in the description. If the goal is to add, update, or remove seed data, provide a brief overview of what specific data is affected and why these changes are necessary.
  • If the PR is meant to introduce seed data for development or testing purposes, consider including details about the data structure and how it should be used within the application.
  • In the absence of a diff, it's also recommended to check if the PR was created correctly and if the changes were committed and pushed to the correct branch.

Thanks for using Sourcery. We offer it for free for open source projects and would be very grateful if you could help us grow. If you like it, would you consider sharing Sourcery on your favourite social media? ✨

Share Sourcery

Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.

@tqt97
Copy link
Owner Author

tqt97 commented Feb 18, 2024

fix conflict

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.

1 participant