Merge develop into main – Documentation, Enhancements, and Testing Updates

[DarkRockMountain-admin]

Description

This pull request merges the develop branch into main, introducing key updates that enhance the spacy-ewc library's usability, functionality, and documentation.

• Related Issue:
• Type of Change:
  • New feature (non-breaking change that adds functionality)
  • Documentation update (to include expanded content)
  • Bug fix (for minor improvements and test coverage)

Checklist

Please ensure the following guidelines are met:

• The code follows the style guidelines of this project.
• A self-review has been performed on the code.
• The code is well-documented, and comments have been added where necessary.
• Tests have been added to prove that the fix is effective or that the feature works. All existing tests pass.
• Commit messages follow the convention type(scope): description.
• The pull request has no conflicts with the base branch.
• Any dependent changes have been merged and published in downstream modules.

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[JRocabruna]

Comments

The merge of the develop branch into main introduces significant enhancements. These changes collectively enhance the usability and functionality of the spacy-ewc library.

Review Checklist

• Code adheres to the project's coding guidelines.
• Changes are well-documented.
• Tests have been added/updated and pass successfully.
• Commit messages follow the correct format: type(scope): description.
• No conflicts with the base branch.

Approval

Approved: The changes meet the project's contribution standards and are ready for integration into the main branch.