Skip to content

Conversation

@everleepham
Copy link
Contributor

Pull Request

Description

Related Issues

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

  • Unit tests
  • Integration tests
  • Manual testing

Checklist:

  • My code follows the project's coding style
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

DebojyotiMishra and others added 30 commits March 31, 2025 12:10
feat(core): initialize Android project with MVVM and Firebase
chore(config): add Firebase configuration and gitignore
test(profile): add TestFile.java for test commit
Fix: Add dummy google-services.json for CI and suppress compileSdk wa…
- Add email/password authentication - Implement user data storage in Firestore - Add profile picture storage in Firebase Storage - Create login and signup UI - Add password reset and email verification features
fix(auth): correct import paths for activities
feat(ui): redesign login and signup screens with dark theme
everleepham and others added 28 commits April 16, 2025 16:04
feat(home): push post on feed
feat(home): clean test button and add delete post function
feat(feed): add delete post feature
fix bugs related to aspect ratio error
docs(readme): adjust readme
fix: complete and clean up code
feat(README): edit README file
@gitguardian
Copy link

gitguardian bot commented Apr 17, 2025

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
- - Cloudinary API keys c3fdbc8 app/src/main/java/com/pineapple/capture/utils/CloudinaryManager.java View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@everleepham everleepham merged commit ca68c01 into main Apr 17, 2025
2 of 3 checks passed
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.

5 participants