Skip to content

Remove Ingenico/Ogone integration#429

Merged
remcotolsma merged 1 commit intomainfrom
428-remove-ingenicoogone
Jan 5, 2026
Merged

Remove Ingenico/Ogone integration#429
remcotolsma merged 1 commit intomainfrom
428-remove-ingenicoogone

Conversation

@remcotolsma
Copy link
Copy Markdown
Member

No description provided.

@remcotolsma remcotolsma self-assigned this Jan 5, 2026
@remcotolsma remcotolsma linked an issue Jan 5, 2026 that may be closed by this pull request
@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @remcotolsma, 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 focuses on a comprehensive removal of the Ingenico/Ogone payment gateway integration. The changes span across core plugin logic, dependency declarations, and documentation, ensuring that all references and functional code related to this specific gateway are deprecated and eliminated. This effort aims to reduce the project's maintenance surface and keep the list of supported integrations current and accurate.

Highlights

  • Integration Removal: The entire Ingenico/Ogone payment gateway integration has been systematically removed from the codebase.
  • Dependency Management: The wp-pay-gateways/ogone dependency has been removed from composer.json and composer.lock, streamlining project dependencies.
  • Configuration Cleanup: All related configuration entries for Ingenico/Ogone have been removed from src/gateways.json, src/providers.json, and src/dev.php.
  • Documentation Update: The README.md and readme.txt files have been updated to reflect the removal of Ingenico/Ogone from the list of supported payment methods.

🧠 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
Copy Markdown

@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 correctly removes the Ingenico/Ogone integration. The changes are consistent across all modified files. I've left one comment regarding a discrepancy in the changelog that should be addressed to ensure release notes are accurate.

Comment thread composer.json
"wp-pay-gateways/ems-e-commerce": "^4.4",
"wp-pay-gateways/mollie": "^4.18",
"wp-pay-gateways/multisafepay": "^4.6",
"wp-pay-gateways/ogone": "^4.8",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

This dependency is correctly removed as part of the Ingenico/Ogone integration removal. However, I've noticed a discrepancy in the changelogs. Both readme.txt (line 160) and CHANGELOG.md (line 68) state that wp-pay-gateways/ogone was updated, which contradicts this removal. Please update the changelogs to reflect that this integration has been removed to avoid confusion.

@remcotolsma remcotolsma merged commit 3ee00a6 into main Jan 5, 2026
17 of 19 checks passed
@remcotolsma remcotolsma deleted the 428-remove-ingenicoogone branch January 5, 2026 18:42
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.

Remove Ingenico/Ogone

1 participant