-
Notifications
You must be signed in to change notification settings - Fork 7
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
WIP Merging #1914
Conversation
Greetings from your nice fit 🤖 !
Check the report carefully, and please buy me a ☕ , or better, a GPU 😉! |
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... |
Co-authored-by: Roy Stegeman <roystegeman@live.nl>
Co-authored-by: Roy Stegeman <roystegeman@live.nl>
Co-authored-by: Roy Stegeman <roystegeman@live.nl>
Co-authored-by: Roy Stegeman <roystegeman@live.nl>
…nerate_dense and generate_dense_per_flavour
Co-authored-by: Juan M. Cruz-Martinez <juacrumar@lairen.eu>
Co-authored-by: Juan M. Cruz-Martinez <juacrumar@lairen.eu>
595e3a9
to
8cb04b3
Compare
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. |
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)