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

refactor(Dependency management): Remove redundant dependencies from build.gradle #426

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

aslamhossin
Copy link

@aslamhossin aslamhossin commented Mar 1, 2023

This commit refactors the build.gradle file for the ActivityEmbeddingWithPredictiveBack sample app by removing two duplicate dependencies. The redundant dependencies were causing potential conflicts and slowing down the build process. By removing these duplicates, the build process is now more efficient and the project's dependency management is improved. The scope of this change is limited to the build.gradle file, and the impact is primarily on the build process and dependency management.

@google-cla
Copy link

google-cla bot commented Mar 1, 2023

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

…uild.gradle

- This commit refactors the build.gradle file for the ActivityEmbeddingWithPredictiveBack sample app by removing two duplicate dependencies. The redundant dependencies were causing potential conflicts and slowing down the build process. By removing these duplicates, the build process is now more efficient and the project's dependency management is improved. The scope of this change is limited to the build.gradle file, and the impact is primarily on the build process and dependency management. The commit message follows the conventional format of starting with a verb, indicating the type of change, and including a brief description of the change and its scope.
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