fix: APP-872 migrating project from collaborators tab

[blushi]

Description

https://regennetwork.atlassian.net/browse/APP-872

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• provided a link to the relevant issue or specification
• provided instructions on how to test
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

How to test

Try to migrate one of your personal project to your organization from the "migrate project" button under "Project collaborators" from projects dashboard

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed all author checklist items have been addressed
• reviewed code correctness and readability
• verified React components follow DRY principles
• reviewed documentation is accurate
• reviewed tests
• manually tested (if applicable)

[gemini-code-assist]

Summary of Changes

Hello @blushi, 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 implements a targeted fix for an issue (APP-872) related to the project migration functionality. The change specifically refines how the 'Migrate Project' button's click event is handled, ensuring the underlying migration logic executes correctly without receiving an unexpected event object. This minor adjustment enhances the robustness and reliability of the project migration process.

Highlights

• Project Migration Button Fix: Corrected the onClick handler for the 'Migrate Project' button to prevent the synthetic event object from being implicitly passed as the first argument to the migrateProject function. This ensures the function is called as intended, resolving a potential issue with project migration.

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

[blushi]

@erikalogie @S4mmyb see testing instructions

[netlify]

✅ Deploy Preview for terrasos ready!

Name	Link
🔨 Latest commit	a918fac
🔍 Latest deploy log	https://app.netlify.com/projects/terrasos/deploys/6978df6ca21177000814b5f9
😎 Deploy Preview	https://deploy-preview-2797--terrasos.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[gemini-code-assist]

Code Review

This pull request correctly addresses a potential issue where a click event handler was being passed directly to a function that does not expect any arguments. By wrapping the migrateProject call in an anonymous arrow function, the code now ensures that migrateProject is called with the correct signature. The use of the void operator is a good practice to explicitly ignore the returned promise and prevent potential linter warnings about unhandled promises. The change is a solid improvement for code correctness and robustness. I have no further suggestions.