Use exit status to determine LJD failure #140
Owner
No description provided.
lucas
added 1 commit 2023-11-17 10:03:24 +01:00
All checks were successful
lint/clippy Checking for common mistakes and opportunities for code improvement
build/msvc Build for the target platform: msvc
build/linux Build for the target platform: linux
lucas
added 1 commit 2023-11-17 15:10:54 +01:00
All checks were successful
lint/clippy Checking for common mistakes and opportunities for code improvement
build/msvc Build for the target platform: msvc
build/linux Build for the target platform: linux
Merge pull request 'Use exit status to determine LJD failure' (#140) from feat/ljd into master
No reviewers
Labels
No labels
ci
crate/dtmm
crate/dtmt
crate/sdk
crate/serde_sjson
kind
bug
kind
documentation
kind
enhancement
kind
feature
kind
question
kind
upstream
part/bundle
part/filetype
stage
actionable
stage
design
stage
proposal
status/duplicate
status/good first issue
status/help wanted
status/invalid
status
need-replicate
status/wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: bitsquid_dt/dtmt#140
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "feat/ljd"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?