Only copy data into CEPH from clean branches

[glopesdev]

During the fast paced development cycle of the presocial workflows, we have been neglecting to do as many PRs to main as we would otherwise recommend. This will make it much harder to document in detail the changes we have addressed along the way once we finally merge everything back to the default branch.

The goal of this proposal is to promote fast iteration cycles on documentation, and motivate the use of both PRs and code review to further improve communication across arena developments.

The proposal is to allow experiments to copy collected data into CEPH for ingestion only when running off the repository main branch with no local modifications. Epochs collected using clean development branches would also be copied into CEPH but into a special devdata root folder which is not targeted for database ingestion. This will allow sharing debug test data for analysis within the team without contaminating stable datasets.

Finally, local tests should be allowed without disabling the export metadata script, which has been circumvented multiple times and ends up copying data into CEPH with no provenance information. Epochs collected using local uncommitted changes would be copied to a separate local folder which is not targeted by the robocopy script.

To achieve this the following steps would have to be resolved:

• ~Modify export metadata script to return a value indicating whether branch is default and repo is clean~
• ~Ensure data is transferred into devdata when repo is clean but current branch is not the default branch~
• [x] Ensure data is logged using current branch name or separate local folder when repo is not clean
• [x] #266
• [x] #267

[glopesdev]

@jkbhagatio @Dario55 @lorycalca @aspaNeuro

[glopesdev]

Following meeting we decided on the following action points:

• Keep all experiments in same repo.
• Dataset name / folder in CEPH is name of branch in aeon_experiments
• main branch is vanilla template
• (optional) check if there is a folder created in CEPH matching that branch name, and prompt for validation
• Add branch protection rule on main to avoid accidental PRs on template
• Other branch protection rules can be applied on a per-branch basis as needed