Pre-release merge into Main

[M-casado]

Summary

Merging dev into main before doing the first official release of the GitHub repository. Timed prior to the submission of D4.3.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New content (non-breaking change which adds new content)
• Modified content (non-breaking change which modifies existing content)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Motivation and Context

There are three SOPs that have finished the development process and are ready to be part of the main GitHub repository. It's motivated by the ulterior submission of Deliverable 4.3.

References

NA

Changes Introduced

• Added three new SOPs
• Slightly modified the linting script

Review

SOPs have been reviewed individually (by reviewers, approvers and MB).

Additional Notes

NA

Checklist:

General Compliance:

• My changes follow the code style of this project (GDI SOP Style Guide) and the file naming conventions of the file accessioning proposal.
• I have verified that all new updated content is accessible, including checking that all external references are readable (i.e., no broken links). These may include references to external resources that should be resolvable, and internal references among SOPs.
• I have properly added this PR's changes to the repository CHANGELOG.md.

Only applicable if the PR includes new, or changes to, GDI SOPs (i.e., documents at sops/):

• My SOP-related changes adhere to the Generic SOP Template, including format and required fields.
• I have consulted the Charter, ISM, and ORR documents to ensure compliance.
• I am complying with the established procedure for SOP creations and modifications, including respecting review phases and notifying needed contributors for reviews.