Set up github pages #39
Conversation
|
Warning Rate Limit Exceeded@cp-pratik-k has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 37 minutes and 50 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. WalkthroughThe Cloud Gallery app by Canopas Software LLP has evolved significantly with the addition of a privacy policy and terms & conditions, improved README structure, and a new dependency for enhanced functionality. Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
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 as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Out of diff range and nitpick comments (27)
docs/terms-and-conditions.md (13)
3-3: Consider using a heading for "Effective Date" instead of bold emphasis for better document structure and readability.
5-5: Consider using a heading for "Welcome to Cloud Gallery!" instead of bold emphasis for better document structure and readability.
9-9: Consider using a heading for "License to Use" instead of bold emphasis for better document structure and readability.
18-18: Consider using a heading for "User Content" instead of bold emphasis for better document structure and readability.
22-22: Consider using a heading for "Third-Party Services" instead of bold emphasis for better document structure and readability.
26-26: Consider using a heading for "Disclaimers" instead of bold emphasis for better document structure and readability.
30-30: Consider using a heading for "Limitation of Liability" instead of bold emphasis for better document structure and readability.
34-34: Consider using a heading for "Termination" instead of bold emphasis for better document structure and readability.
38-38: Consider using a heading for "Entire Agreement" instead of bold emphasis for better document structure and readability.
42-42: Consider using a heading for "Governing Law" instead of bold emphasis for better document structure and readability.
46-46: Consider using a heading for "Changes to the Terms" instead of bold emphasis for better document structure and readability.
50-50: Consider using a heading for "Contact Us" instead of bold emphasis for better document structure and readability.
55-55: Ensure the file ends with a single newline character to adhere to POSIX standards.docs/privacy-policy.md (14)
1-1: Consider using a heading for "Cloud Gallery Privacy Policy" instead of bold emphasis for better document structure and readability.
3-3: Consider using a heading for "Effective Date" instead of bold emphasis for better document structure and readability.
5-5: Consider using a heading for "Introduction" instead of bold emphasis for better document structure and readability.
9-9: Consider using a heading for "Information We Collect" instead of bold emphasis for better document structure and readability.
16-16: Consider using a heading for "Google Drive Information (Optional)" instead of bold emphasis for better document structure and readability.
30-30: Consider using a heading for "How We Use Your Information" instead of bold emphasis for better document structure and readability.
42-42: Consider using a heading for "Sharing Your Information" instead of bold emphasis for better document structure and readability.
52-52: Consider using a heading for "Data Retention" instead of bold emphasis for better document structure and readability.
58-58: Consider using a heading for "Your Choices" instead of bold emphasis for better document structure and readability.
68-68: Consider using a heading for "Security" instead of bold emphasis for better document structure and readability.
72-72: Consider using a heading for "Children's Privacy" instead of bold emphasis for better document structure and readability.
76-76: Consider using a heading for "Changes to this Policy" instead of bold emphasis for better document structure and readability.
80-80: Consider using a heading for "Contact Us" instead of bold emphasis for better document structure and readability.
85-85: Ensure the file ends with a single newline character to adhere to POSIX standards.
Summary by CodeRabbit
privacy-policy.mdfile outlining the privacy practices of the Cloud Gallery mobile application.terms-and-conditions.mdfile outlining the Terms & Conditions for the Cloud Gallery mobile application.package_info_plus-8.0.0dependency to the project configuration.