Skip to content

docs(fix): PyInvoke replaced by just #70

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

Merged
merged 3 commits into from
Apr 10, 2025

Conversation

fabianbergermann
Copy link
Contributor

Changes

update the section on DAGs in README.md reflecting the replacement of PyInvoke by just

Reasons

Brings the readme up to date in this minor point

Impacts

Only the documentation

Notes

This is my first little contribution. Just offering, in case you accept external PRs.
Either way, many thanks for this great project!

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.

Hello @fabianbergermann, 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 updates the README.md file to reflect the replacement of PyInvoke with just for the DAG example. The change involves modifying the documentation to point to tasks/project.just instead of tasks/dags.py and updating the description to mention Just instead of PyInvoke. This keeps the documentation up-to-date with the current project setup.

Highlights

  • Documentation Update: The README.md file has been updated to reflect the change from PyInvoke to just for the DAG example.
  • DAG Example: The documentation now points to tasks/project.just for the DAG example, which uses just.

Changelog

  • README.md
    • Replaced PyInvoke with just in the DAG example description.
    • Updated the DAG example file path from tasks/dags.py to tasks/project.just.
    • Updated line 916 to reflect the change in tooling.
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.

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

The pull request updates the README.md file to reflect the replacement of PyInvoke with just for the DAG example. The changes are straightforward and seem correct. However, I have a suggestion to improve clarity.

Merge Readiness

The pull request is a simple documentation update and appears ready to be merged. I am unable to directly approve the pull request, and recommend that others review and approve this code before merging.

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@fabianbergermann fabianbergermann changed the title docs(fix): PyInvoke replaced just docs(fix): PyInvoke replaced by just Apr 9, 2025
@fmind fmind self-assigned this Apr 10, 2025
@fmind
Copy link
Owner

fmind commented Apr 10, 2025

Merged! Thanks for the contrib @fabianbergermann :)

@fmind fmind merged commit 856a5ab into fmind:main Apr 10, 2025
1 check passed
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.

2 participants