Skip to content

[T1142] New Suspension Communication Rules#2069

Open
avuff wants to merge 11 commits into14.0from
T1142-new-suspension-com-rules
Open

[T1142] New Suspension Communication Rules#2069
avuff wants to merge 11 commits into14.0from
T1142-new-suspension-com-rules

Conversation

@avuff
Copy link

@avuff avuff commented Jan 27, 2026

No description provided.

ecino and others added 11 commits October 2, 2025 15:14
- For MyCompassion2, the order of the attachments need to be reversed
* T2624 Add callbacks for pdf generation

* T2288 Force-the-maximum-pages-of-a-letter-to-be-15 (#2051)

* Reapply "Add page nb check"

This reverts commit 8d4d27f.

* Run precommit

* Add args safety to callbacks

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Remove redundant error raised

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Remove callbacks

* Code improvements

* Fix concurency cohenrence

* Fix error propagation when more than 15 pages

* Run precommit

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Emanuel Cino <ecino@compassion.ch>
Remove unecessary update_nb_sposorships

Refactor names and run precommit
…-it-should-be-one-is-an-isolated-case' into 14.0-MyCompassion2
* Fix sytax error.

* Refactor and ensure atomiity of transaction

* Fix concurrency problem

* Refactor and add comments

* Remove typos

* Update sbc_compassion/models/correspondence_s2b_generator.py

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update sbc_compassion/models/correspondence_s2b_generator.py

Fix sytax error.

Refactor and ensure atomiity of transaction

Fix concurrency problem

Refactor and add comments

Remove typos

Co-Authored-By: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Remove unecessary cursors creation

* Refactor

* Rollback changes

* Define isaolated_write and refactor

* Reorder the DONE status update

* Allow updating the generation status from the back end

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
# Conflicts:
#	sbc_compassion/models/correspondence_s2b_generator.py
#	sponsorship_compassion/models/res_partner.py
* Restirct notif. to only hold of type SUB_CHILD_HOLD

* Run precommit

* Correct wrong type of Hold

* Fix typo
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @avuff, 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 significantly enhances the project suspension communication system by automating the notification process for sponsors and streamlining the underlying communication templates. It also brings crucial improvements to the stability and user feedback of the PDF generation utility, making the system more reliable and user-friendly.

Highlights

  • Automated Suspension Communication: Introduced a new cron job that automatically identifies projects suspended for over two months and triggers appropriate communication (initial announcement or follow-up) to sponsors.
  • Streamlined Communication Templates: Replaced multiple project suspension extension and reactivation email templates with a single, more flexible 'Project Suspension Follow Up' template, simplifying the communication workflow.
  • Enhanced PDF Generation Robustness: Improved the PDF generation process for correspondence by adding status tracking, better error handling, and a maximum page count limit to prevent the creation of excessively long documents.
  • Migration for Obsolete Configurations: Added a pre-migration script to safely remove outdated communication configurations and their associated email templates from the database, ensuring a clean upgrade.

🧠 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
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 introduces new suspension communication rules, including a cron job to manage project suspension announcements and follow-ups. It also significantly enhances the robustness and user feedback for the S2B (Sponsor-to-Beneficiary) letter generation process by adding detailed status tracking, improved error handling, and better resource management for temporary files. Obsolete communication configurations and email templates have been removed, and a migration script is provided to clean up old data.

<record id="ir_cron_suspension_announcement" model="ir.cron">
<field
name="name"
>Project: 2-Month Suspension Annoucement/Follow-Up</field>
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

There is a typo in the cron job's name. "Annoucement" should be "Announcement".

Suggested change
>Project: 2-Month Suspension Annoucement/Follow-Up</field>
>Project: 2-Month Suspension Announcement/Follow-Up</field>

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.

4 participants