AGENTS.md for contributors

[galesky-a]

Description
Add an AGENTS.md for contributors.

Tested scenarios
Tested on a couple coding agents by delegating a task before and after adding the files

[gemini-code-assist]

Summary of Changes

Hello @galesky-a, I'm Gemini Code Assist¹! 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 significantly enhances the contributor experience by adding a new "AGENTS.md" file. This document serves as a central resource, clarifying the library's architecture, detailing the automated code generation process, explaining the development workflow, and outlining the release procedures. Its purpose is to provide clear guidance and streamline contributions to the Adyen Python API Library.

Highlights

• New Documentation: Introduced a new "AGENTS.md" file to provide comprehensive guidelines and information for contributors to the Adyen Python API Library.
• Code Generation Explained: Detailed the automated code generation process for API services, including the use of OpenAPI Generator, custom Mustache templates, and instructions for local generation via the "adyen-sdk-automation" repository.
• Core Components Overview: Provided an overview of the library's core components, such as the main facade class, client configuration, HTTP client, and generated service packages.
• Development Workflow: Outlined the development workflow, covering setup, running tests with "tox", and maintaining code style and formatting using "flake8" and "black" via "make" commands.
• Automated Release Process: Described the automated release process managed by GitHub Actions, from version bumping to publishing to PyPI.

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

[gemini-code-assist]

Code Review

This pull request adds an AGENTS.md file to guide contributors, particularly automated agents, on how to work with this repository. The document is well-structured and provides useful information about code generation, core components, and the development workflow. I've provided a couple of suggestions to improve the clarity and correctness of the instructions. One suggestion is to make a path placeholder more concrete for easier use by agents. The other, more critical suggestion, is to correct the commands for linting and formatting, as the ones currently in the document are not defined in the project's Makefile.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[jeandersonbc]

Rebasing and merging changes. Any further improvement can be addressed in a follow-up PR.