Skip to content

Conversation

@HI-JIN2
Copy link
Member

@HI-JIN2 HI-JIN2 commented Jan 29, 2026

릴리즈 브랜치에서 해야하는 일

  • versionCode, versionName
    fastlane 작업 브랜치에서 internal 테스트 올리면서 숫자 하나씩 올렸어가지구 이번에는 versionCode만 바꿈. (인터널이라 상관 없을것 같기도..하지만 혹시 모르니까.. ) (versionName은 똑같아도 되는데 versionCode은 달라야함)
  • releaseNote

@HI-JIN2 HI-JIN2 self-assigned this Jan 29, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @HI-JIN2, 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!

이 Pull Request는 버전 3.2.1 릴리즈를 위한 준비 작업의 일환으로, 애플리케이션의 versionCode를 업데이트하고 릴리즈 노트의 문장 부호를 통일하여 가독성을 높였습니다. 이는 새로운 버전 배포를 위한 필수적인 단계입니다.

Highlights

  • 버전 코드 업데이트: 애플리케이션의 versionCode가 50에서 51로 업데이트되었습니다.
  • 릴리즈 노트 문장 부호 통일: 릴리즈 노트 파일(release-notes/v3.2.1.yml)의 한국어 및 영어 항목 끝에 마침표가 추가되어 문장 부호가 통일되었습니다.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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.

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
Contributor

@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

3.2.1 릴리즈를 위한 PR이네요. versionCode를 업데이트하고 릴리즈 노트를 수정하신 것을 확인했습니다. 전반적으로 좋아 보입니다. 릴리즈 노트 파일의 끝에 개행 문자를 추가하는 작은 개선 사항을 제안합니다.

@HI-JIN2 HI-JIN2 requested a review from PeraSite January 29, 2026 00:51
@github-actions
Copy link

✅ CI 완료

@github-actions
Copy link

✅ CI 완료

@HI-JIN2
Copy link
Member Author

HI-JIN2 commented Jan 29, 2026

워크플로우에러 여기서 고쳣어요.. 죄송슨 ㅠㅠ

@github-actions
Copy link

✅ CI 완료

Copy link
Member

@PeraSite PeraSite left a comment

Choose a reason for hiding this comment

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

👍

@HI-JIN2 HI-JIN2 merged commit 0a18637 into develop Jan 29, 2026
1 check passed
@HI-JIN2 HI-JIN2 deleted the release/3.2.1 branch January 29, 2026 05:03
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.

3 participants