confirmed
(but I need them to tell me what errors of what special remotes need a message-id)
This commit is contained in:
parent
6774f0bf40
commit
f1714915b2
2 changed files with 13 additions and 0 deletions
|
@ -5,3 +5,4 @@ May be even more generally -- if there was a robust way to obtain errors for oth
|
|||
[[!meta author=yoh]]
|
||||
[[!tag projects/datalad]]
|
||||
[[!tag moreinfo]]
|
||||
[[!tag confirmed]]
|
||||
|
|
|
@ -0,0 +1,12 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 3"""
|
||||
date="2023-06-23T20:13:10Z"
|
||||
content="""
|
||||
enableremote supports --json-error-messages now. The error messages are not
|
||||
really machine parseable. But, json error messages can also now be tagged
|
||||
with a unique message-id.
|
||||
|
||||
So, this is entirely implementable, it just needs to determine which
|
||||
specific failures of which special remotes, and add a message-id to them.
|
||||
"""]]
|
Loading…
Add table
Reference in a new issue