Add Latchkey to Continuous Integration & Delivery - #5020
Open
that-developer-kaveh wants to merge 1 commit into
Open
Add Latchkey to Continuous Integration & Delivery#5020that-developer-kaveh wants to merge 1 commit into
that-developer-kaveh wants to merge 1 commit into
Conversation
|
You can preview your changes by visiting this link. Note This feature is still experimental and may not work as expected in some cases. Please report any issues you find! |
Signed-off-by: Kaveh Alemi <kvalemi98@gmail.com>
that-developer-kaveh
force-pushed
the
add-latchkey
branch
from
August 6, 2026 05:47
d55d7c6 to
525a687
Compare
This file contains hidden or 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
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.
Adds Latchkey to App Definition and Development > Continuous Integration & Delivery, in alphabetical order between Keptn and Liquibase.
Latchkey provides managed ephemeral Linux runners for GitHub Actions. When a step fails, agents diagnose the cause and repair it at runtime before retrying, rather than the job simply going red. Real defects such as compile errors and failing tests are never retried or masked.
Against the guidelines in the README:
landscape.ymlparses cleanly after the change.Disclosure: I'm a co-founder of Latchkey.