Conversation
Pull Request Test Coverage Report for Build 3910411035Details
💛 - Coveralls |
4627950 to
cbeb99c
Compare
8a2333c to
2b9f860
Compare
|
Waiting for #2094... I will step by step adding migrations from the discussion.. so... I will make this a draft now, because it will take a little longer as expected :) |
|
What about if we continue the pipeline, even if the spell check fails? @jnyrup or @dennisdoomen |
Somehow I thought that was already how it worked since But yes, |
|
This is a really tricky task.. I am checking now if I can overcome this issue |
|
Oh... that's too easy.. 🙈 Checking now the other way round.. a second please Edit: seems good :) take that solution 🎉 |
2b9f860 to
3493738
Compare
232822d to
7943554
Compare
f4d01d5 to
b1fadf1
Compare
Build.cs: Deduplicate code elements, remove dead codeBuild.cs: Deduplicate code elements, generating workflow yaml files
|
Ok.. just to make sure we are in sync here: |
I quickly glanced at the PR and most seems legit, but we still need to do a thorough review. |
Build.cs: Deduplicate code elements, generating workflow yaml filesBuild.cs: Deduplicate code elements
03bdcc4 to
726319d
Compare

IMPORTANT
./build.sh --target spellcheckor.\build.ps1 --target spellcheckbefore pushing and check the good outcomeThis PR does following
GitHubActionswhich will be injected by NUKE at build startApiKeyto more specificNuGetApiKey