Skip to content

Update repository count and implement dynamic fetch in workflow#11

Open
Devanik21 wants to merge 1 commit intomainfrom
jules-10334846330115920507-22ac5f39
Open

Update repository count and implement dynamic fetch in workflow#11
Devanik21 wants to merge 1 commit intomainfrom
jules-10334846330115920507-22ac5f39

Conversation

@Devanik21
Copy link
Owner

This change updates the repository count in README.md to reflect the current state (188). It also updates .github/workflows/research-log.yml to dynamically fetch the repository count from the GitHub API (https://api.github.com/users/Devanik21) when generating the daily monograph, so the number stays up to date automatically. Past historical logs in docs/ecosystem_monograph.md were reverted to their original state to preserve data integrity.


PR created automatically by Jules for task 10334846330115920507 started by @Devanik21

- Updated the static repository count in README.md to the current value (188).
- Modified the `.github/workflows/research-log.yml` to dynamically fetch the repository count from the GitHub API when the workflow runs, ensuring future log entries are always accurate.
- Preserved historical log entries in `docs/ecosystem_monograph.md` which had previously been incorrectly modified.

Co-authored-by: Devanik21 <162272415+Devanik21@users.noreply.github.com>
@google-labs-jules
Copy link
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@gemini-code-assist
Copy link

Summary of Changes

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

This pull request enhances the accuracy and automation of repository count reporting. It updates the static repository count in the README.md to its current value and introduces a dynamic fetching mechanism in the GitHub Actions workflow to automatically keep this count up-to-date using the GitHub API. Additionally, it addresses data integrity by reverting historical log entries.

Highlights

  • Repository Count Update: The README.md file was updated to reflect the current repository count of 188, down from 270, in various sections.
  • Dynamic Count Automation: The .github/workflows/research-log.yml workflow was modified to dynamically fetch the repository count from the GitHub API, ensuring the number remains current.
  • Historical Log Integrity: Past historical logs in docs/ecosystem_monograph.md were reverted to their original state to preserve data integrity.

🧠 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.

Changelog
  • README.md
    • Updated the displayed total repository count from 270 to 188 in the badge.
    • Revised the "Engineering Impact" section to reflect 188 active repositories.
    • Adjusted the "What I Bring" section to state 188 repositories.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/research-log.yml
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

@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 updates the hardcoded repository count in README.md. While the PR description mentions that a workflow is being implemented to dynamically fetch this count for a daily monograph, the README.md file itself is still being updated manually. My review includes a suggestion to extend the automation to the README.md file to ensure the count remains accurate over time and to resolve the existing TODO comments.

[![arXiv](https://img.shields.io/badge/arXiv-Research-b31b1b.svg?style=for-the-badge)](https://arxiv.org/abs/2412.20091)

![Total Repositories](https://img.shields.io/badge/Total_Repositories-270-4B0082?style=for-the-badge) <!-- TODO: Consider automating the update of this repository count to keep it dynamically current. -->
![Total Repositories](https://img.shields.io/badge/Total_Repositories-188-4B0082?style=for-the-badge) <!-- TODO: Consider automating the update of this repository count to keep it dynamically current. -->

Choose a reason for hiding this comment

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

medium

Since you are already fetching the repository count dynamically in a workflow, consider extending that automation to update this README.md file as well. This would resolve the TODO comment and ensure the repository count is always up-to-date without manual changes. A common approach is to use placeholders in the README that a workflow can replace with live data.

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