Pre-merge branch for batch of changes

[scarlehoff]

Dummy branch to merge the latest changes to a single branch and run tests before merging to master.

Incidentally, I just found a bug either on the way github calls the workflow or the way in which we configured it.

[scarlehoff]

@APJansen I'm going to run the bot on my batch of branches and then I will merge yours and do the same. I'll try to rebase them (they should be 100% independent and try to fix any small conflicts myself)

I will do:

#1881
then
#1888

Is the order correct? Or should I only merge one of them because it contains the other?

[APJansen]

#1888 branches directly off master and has been reviewed, so it can be merged here.
#1881 branches off of #1888, and I think still needs to be reviewed.

So perhaps you can merge #1888, I'll rebase #1881 on this branch and then it can be reviewed before merging here?

#1905 branches off of #1888, so this should wait for that.

The destroyingc++ label along with the very large diff looks great btw ;P

[scarlehoff]

Ok! Perfect.

I now need to understand how to tell github actions that this is not, in fact, master...

[github-actions]

Greetings from your nice fit 🤖 !
I have good news for you, I just finished my tasks:

• Fit Name: NNBOT-a3543991c-2024-01-19
• Fit Report: https://vp.nnpdf.science/B6njNUOQQuOM2jpy_tOozQ==
• Fit Data: https://data.nnpdf.science/fits/NNBOT-a3543991c-2024-01-19.tar.gz

Check the report carefully, and please buy me a ☕ , or better, a GPU 😉!