setting up CI for the repo

[grg2rsr]

No description provided.

[grg2rsr]

#11

[grg2rsr]

in the process of removing ONE from test_plots.py, I had to change the hard coded column key stimOnTrigger_times to stimOn_times. I used the same files as specified in the eid and grabbed the data from the mainenlab server, and stimOnTrigger_times is not present in trials.table, but stimOn_times is and tests are passing. I wonder how this came about, were there different extraction runs, and @GaelleChapuis has locally a different dataset then what is stored on the server? solved.
Additionally, I think it might be better to have the tests based on data from Caronlina, as they were run with an extractor that we are going to re-use in the future.

[bimac]

All good if the CI is running - which it seems to do.

Just a few opinions:

• Use actions/setup-python@v5
• Caching makes GH workflows a lot snappier as you don't have to set up the environment from scratch each time, see https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows
• I personally use PDM as a package manager - it simplifies a few things about the GH workflow (especially when it comes to publishing at some point) - happy to walk you through it if you're interested
• it might be useful to save the versions of dependencies as a workflow artifact (requirements-frozen.txt)
• how about adding coverage? you could use the pytest-cov plugin for that ...