Release Version '1.12.2' into 'master' Branch #166
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
* ci(gitops): rename automatically created "boarding to train" branch, to 'boarding-auto'
* ci(gitops): fix syntax of merge-rt-in-release Workflow
* ci(gitops): fix merge-rt-in-release Workflow
* test: Regression and Backwards Compatibility
Add Automated Regression Test for 'Generator Docs Default Settings'. By Default Generator v2.x promises that upon invocation, the generated Project with be configured for Doc Builds with Sphinx and RTD Python3.8. The Test will fail if Defaults change. If Test is fixed, then this is evidence that if changes are released, they possibly introduce "breaking changes". Also, we add a new Test on the Dialog Prompts to verify that they prompt User for each and every one of the Cookiecutter Tempalte Variables. If this test fails, then the Dialog System and the Cookiecutter Tempalte Vars are out of Sync, which should be addressed, preventing a Bug from shipping Code with the 2 components being NOT synced. From this commit and on, we also stop include Code Coverage for Test Code ('tests' dir), but rather only for the Production Code, in 'src' dir.
Tests, for automatic compati and increase Testsmeasure Code Coverage only for Code in 'src', and not 'tests', dir
test(dialog-system): verify prompts user for each and everyone of Cookiecutter Template Variables
test(docs-settings): verify Gen Project configured with Sphinx and RTD Py3.8, as advertised Defaults
refactor(isort): apply isort
refactor(black): apply black
* ci(gitops): simplify logic and debug
* ci(gitops): fix syntax of merge-rt-in-release workflow
* ci(gitops): track remote branches only if they do not exist locally
---------
Co-authored-by: konstantinos <[email protected]>
Co-authored-by: Konstantinos Lampridis <[email protected]>
boromir674
temporarily deployed
to
TEST_DEPLOYMENT
GitHub Actions
Inactive
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #166 +/- ##
==========================================
+ Coverage 83.71% 88.42% +4.71%
==========================================
Files 77 53 -24
Lines 1989 916 -1073
==========================================
- Hits 1665 810 -855
+ Misses 324 106 -218
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
boromir674
previously approved these changes
Feb 7, 2024
boromir674
added
test
backwards-compatible
This reverts commit c8aa691.
boromir674
approved these changes
Feb 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚀 Release '1.12.2' into 'master' Branch 🚀
This PR marks a pivotal moment in our deployment cycle, signaling that all changes on the Release branch are deemed ready for production. It represents the collective decision of our developers that the changes bundled in the Release are suitable to be released together.
What's Happening in This PR?
✅ Automatic Merging Upon CI Checks ✅
This PR will be automatically merged into the 'master' branch, if the following conditions are met:
If the above conditions are not met, this PR will be manually merged into the 'master' branch, by a developer.