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

[Infra] Remove social_media_url attribute from podspecs. #14554

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

Conversation

ncooke3
Copy link
Member

@ncooke3 ncooke3 commented Mar 10, 2025

Diff LGTM:

git grep --name-only social_media_url -- *.podspec | wc -l
      23

#no-changelog

This change removes the  attribute from all affected podspec
files in the repository. This attribute is no longer needed. No new tests
were added, but the existing test suite is not available in this environment.
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Hello @ncooke3, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

This pull request removes the social_media_url attribute from multiple podspec files in the Firebase iOS SDK repository. The change affects 23 files, as indicated by the git grep command in the PR description. The removal appears to be a straightforward deletion of a single line in each of the affected .podspec files.

Highlights

  • Removal of social_media_url: The primary change is the removal of the s.social_media_url = 'https://twitter.com/Firebase' line from various .podspec files.
  • Infrastructure Change: This pull request is categorized as an infrastructure change, suggesting it's related to the project's setup and configuration rather than functional code.

Changelog

Click here to see the changelog
  • Firebase.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseABTesting.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseAppCheck.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseAppCheckInterop.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseAuth.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseAuthInterop.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseCombineSwift.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseCore.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseCoreExtension.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseCoreInternal.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseDatabase.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseDynamicLinks.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseInAppMessaging.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseInstallations.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseMLModelDownloader.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseMessaging.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseMessagingInterop.podspec
    • Removed the s.social_media_url attribute.
  • FirebasePerformance.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseRemoteConfig.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseRemoteConfigInterop.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseSessions.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseStorage.podspec
    • Removed the s.social_media_url attribute.
  • FirebaseVertexAI.podspec
    • Removed the s.social_media_url attribute.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.


Trivia time!

What is the purpose of a Podspec file in CocoaPods?

Click here for the answer
A Podspec file is a specification that describes a library. It includes details such as the name, version, source location, and dependencies of the library, allowing CocoaPods to integrate it into a project.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request removes the social_media_url attribute from multiple podspec files. The change seems straightforward and aligns with the goal of cleaning up the podspecs. However, it's worth considering if there's a better place to store this information, perhaps in a central configuration file or a dedicated metadata service, if it's still needed.

Merge Readiness

The pull request appears to be a simple removal of an attribute, and the changes are localized. Given the absence of any identified high or critical severity issues, the pull request seems to be in good shape to be merged. However, I am unable to directly approve the pull request, and users should have others review and approve this code before merging.

Copy link
Contributor

@andrewheard andrewheard left a comment

Choose a reason for hiding this comment

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

As a heads up, we do still post to https://x.com/Firebase. I saw a similar test failure when the URL couldn't be validated: https://github.com/firebase/firebase-ios-sdk/actions/runs/13770006231/job/38506345276?pr=14547#step:6:35

It seems to be showing as WARN, not NOTE. When it occurred, I also couldn't access Twitter from my browser so maybe they had a temporary outage.

I think we should ask @peterfriese before merging this. Some options would be to update the URLs to https://x.com/Firebase from https://twitter.com/Firebase or, my preference, switching to the YouTube channel https://www.youtube.com/firebase (but Peter would know best).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants