Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP Merging #1914

Merged
merged 66 commits into from
Jan 24, 2024
Merged

WIP Merging #1914

merged 66 commits into from
Jan 24, 2024

Conversation

scarlehoff
Copy link
Member

@scarlehoff scarlehoff commented Jan 19, 2024

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

Reopening this branch with a change in the concurrency rules as I just realized that parallel branches had the same ref

Fitbot for the python part: #1913 (comment)

Rules to merge the other 2 PR: #1913 (comment)

@scarlehoff scarlehoff requested a review from APJansen January 19, 2024 13:40
@scarlehoff scarlehoff added destroyingc++ devtools Build, automation and workflow Refactoring escience run-fit-bot Starts fit bot from a PR. labels Jan 19, 2024
Copy link

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

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

@scarlehoff
Copy link
Member Author

scarlehoff commented Jan 23, 2024

I'm going to merge this. I want to make sure that anything starting new branches off here.

#1881 and #1799 will be merged to master probably later this week unless problems are found during the review.

Edit: I wonder whether anyone other than @Radonirinaunimi has tested this but the sooner we start using it the sooner we find the possible bugs...

@scarlehoff scarlehoff force-pushed the develop_merge_20240119 branch from 595e3a9 to 8cb04b3 Compare January 24, 2024 08:50
@scarlehoff
Copy link
Member Author

force-pushed and rebase before merging to be absolutely sure that no commit sneaks in before the 4.0.8 tag

I know it might not be feasible to do this with all PRs but I really want the history prior to that tag to be completely clean in case we find any bugs and have to understand which fits are affected. As soon as the tests are done I'll merge this to master.

@scarlehoff scarlehoff merged commit af3306a into master Jan 24, 2024
8 checks passed
@scarlehoff scarlehoff deleted the develop_merge_20240119 branch January 24, 2024 09:32
@scarlehoff scarlehoff removed the run-fit-bot Starts fit bot from a PR. label Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants