Release Version '1.12.1' into 'master' Branch #155
Closed
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}
…elease-train Branch (#149) * ci(gitops): 1-click boarding on Release Train ci(gitops): mention User's branch name in PR title ci(gitops): debug why train branch is missing ci(gitops): use origin/release-train to merge 'boarding' branch into ci(gitops): use local refs for PR, and include sanity check prior to opening PR ci(gitops): try to trigger Boarding CI Checks, related to PR --> 'release-train', by pushing 'boarding' br after PR open ci(gitops): trigger on PR from boarding to release-train for for test.yaml Workflow ci(gitops): use pat, instead of GITHUB_TOKEN, to trigger CI/CD Pipeline in push from Workflow code ci(gitops): use pat, instead of GITHUB_TOKEN, to trigger CI/CD Pipeline in push from Workflow code ci(gitops): do do git push 'boarding' branch after PR opens ci(gitops): write proper Markdown content for PR Body ci(gitops): automatically merge boarding --> release-train PR, once CI Checks Pass ci(gitops): fix Boarding Train event trigger ci(gitops): fix logic of condition to create Release Train ci(gitops): if Upstream Release Train exists, pull it ci(gitops): debug release train branch track upstream error ci(gitops): fix condition when release train does NOT exist ci(gitops): fix condition when release train does NOT exist ci(gitops): improve load bash script ci(gitops): improve load bash script * ci(gitops): add shell script to trigger RC Tests on CI * ci(gitops): handle branches on local dev machine * ci(gitops): start rt by only updating release branch, local and upstream * ci(gitops): make bash script non-interactive * ci(gitops): improve bash script * ci(gh-release): add Job for `gh release create`, and trigger load-to-rt on 'auto-release' tag * chore(start-rt): document option for CLI solution with shell for simple interaction, or with python * ci(gitops): automatically 'board' and 'start' Release Train, on 'boarding-n-auto-release' pushed tag * style(comments): clean code, by removing obsolete code comments about cookiecutter callable * refactor(black): apply black * test(log-file): expect either empty log file in PWD, after generator run, or no file at all * refactor(black): apply black --------- Co-authored-by: konstantinos <[email protected]> Co-authored-by: Konstantinos Lampridis <[email protected]>
ci(gitops): try to fix, by tracking Upstream 'release' branch before checking tag ci(gitops): print git log before checking if tag is on release branch ci(gitops): fix false negative ci(gitops): add script for automatic Sem Ver source code update ci(gitops): chmod +x script in CI workflow ci(gitops): configure git user.name and user.email before ci(gitops): fix path to parse_version.py and use sh as entrypoint to distro-sem-ver-bump.sh ci(gitops): properly git revert to commit with Prod Sem Ver after -rc tests
…ic envrionemnt set
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #155 +/- ##
==========================================
+ Coverage 83.08% 83.15% +0.07%
==========================================
Files 77 77
Lines 1986 1983 -3
==========================================
- Hits 1650 1649 -1
+ Misses 336 334 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
…move GH Release Job
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.1' 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.