Skip to content

Conversation

@yonghanJu
Copy link

변경 사항

기존 문서상 잘못 기재된 레포 url 링크 실제 레포에 맞게 수정

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.

Summary of Changes

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

이 풀 리퀘스트는 조직의 README.md 문서에 포함된 레포지토리 링크의 오타를 수정하여, 사용자들이 정확한 레포지토리로 이동할 수 있도록 문서의 정확성을 향상시키는 것을 목표로 합니다. 이는 문서의 신뢰성을 높이고 잠재적인 혼란을 방지합니다.

Highlights

  • README URL 수정: profile/README.md 파일 내 'Android-Dependency-Tree-Diff-Viewer' 레포지토리 링크의 오타를 수정했습니다. 기존 'Dependency'를 'Dependecy'로 변경하여 실제 레포지토리 이름과 일치하도록 했습니다.
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 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

@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

README.md 파일의 링크를 수정하는 변경 사항을 확인했습니다. 링크의 URL을 실제 저장소 주소에 맞게 수정하면서, 링크 텍스트에도 오타가 반영되었습니다. 링크 텍스트는 사람이 읽는 부분이므로, 가독성을 위해 올바른 철자법을 사용하는 것이 좋습니다. 아래에 관련하여 한 가지 의견을 남겼습니다.

- Compose의 경우 Screen Route를 우측 상단에 오버레이로 표시 (Activity/Fragment도 포함)

[Android-Dependency-Tree-Diff-Viewer](https://github.com/DongLab-DevTools/Android-Dependency-Tree-Diff-Viewer)
[Android-Dependecy-Tree-Diff-Viewer](https://github.com/DongLab-DevTools/Android-Dependecy-Tree-Diff-Viewer)

Choose a reason for hiding this comment

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

medium

링크의 URL을 실제 저장소 이름에 맞게 수정하신 것은 좋습니다. 하지만 링크에 표시되는 텍스트(Android-Dependecy-Tree-Diff-Viewer)에도 오타가 포함되어 있습니다. URL은 링크가 올바르게 동작하도록 오타가 있는 그대로 두어야 하지만, 사용자에게 보여지는 텍스트는 Dependency로 올바르게 표기하여 가독성을 높이는 것이 좋겠습니다.

Suggested change
[Android-Dependecy-Tree-Diff-Viewer](https://github.com/DongLab-DevTools/Android-Dependecy-Tree-Diff-Viewer)
[Android-Dependency-Tree-Diff-Viewer](https://github.com/DongLab-DevTools/Android-Dependecy-Tree-Diff-Viewer)

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