Unverified50% confidenceSolutionExact time
The official workaround is: in filtering scenarios pass refs/heads/null or a commit SHA instead; when creating a new branch from the null branch, first git_checkout and then call git_create_branch without base_branch.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/19/2026
First Seen
Valid until: 1/17/2027
Sources
Related Entities
Related Claims
UnverifiedIn an IF node, data on the false branch terminates by default unless other processing logic is additionally connected.60% similarUnverifiedgit diff --check warns when changes introduce conflict markers or whitespace errors, and exits with a non-zero status when problems are found.60% similarUnverifiedThe way to fix the signal lost by catching an exception is to actively re-mark inside the catch block, for example by calling span.recordException(e) and span.setStatus({ code: SpanStatusCode.ERROR }), and then decide whether to resume execution.59% similarUnverifiedNULLIF returns NULL when its two arguments are equal, and is commonly used in conjunction with division to prevent divide-by-zero errors.57% similarUnverifiedWhen a data row is composed entirely of non-top-left cells of a merge, reading by row yields all nulls, causing that row to be discarded by empty-row filtering logic.57% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1067571API
curl https://kongchang.com/api/v1/knowledge/claims/1067571MCP
get_claim(id=1067571)