Save opportunities

[SarahWohlford]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works (if a larger change)
• New and existing unit tests pass locally with my changes

[deepsource-io]

Here's the code health analysis summary for commits 5e5c5a9..fa2821e. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[RafaelCenzano]

Everything lookg good can you just remove the comments and things that are still in this branch but not main. Just take a look at the files you didn't touch or code you didn't change and make sure it matches main

[RafaelCenzano]

These commented things were removed in main, they should be removed here too