You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Got several rounds of error messages trying to save a file. This needs to be a whole lot better. Below is the process I went through to try to get it to save.
Suggestions:
indicate more clearly in the instruction what is needed
indicate if one or both fields are mandatory
try to autopopulate as far as possible
try to come up with a default option that will work
First something like "Unable to save because of unknown entity" or some such thing, which doesn't tell me what to do to fix it.
Then the error message in the screenshot included here.
How can we make it easier for users? Can we autopopulate the path based on their github account, at least with the ?
These are the values I tried to use:
This is my github user name, and I said yes to creating the repo and the file when prompted. Then I got the permissions message.
I also tried just putting my username in the top box, thus
Then I got the entity error
THEN, I went to my account, and copied the path from the url and put it in, thus:
I said yes to creating a repo (even though the repo already existed) and got this new and not very helpful error message:
Finally I input this:
And I confirmed that I wanted to save to an existing repository and that I wanted to save the file. And it finally worked.
The text was updated successfully, but these errors were encountered:
@SusanBrown , looks like in the first two cases you did not follow the instruction in the dialog box: you either tried to put the full path (including the file name) in the first field, or just the user name
As you can see in the inline instructions (below each of the two fields) you have to specify userID/repoName in the first field and the file path within the repository (including any nested folders) in the second. This is what you did in the end.
I can't remember the specific reasons why saving path is split this way, but I am pretty sure James said it was something that needed to be split this way to ease handling.
Any suggestions on improving the inline documentation are welcome :)
Got several rounds of error messages trying to save a file. This needs to be a whole lot better. Below is the process I went through to try to get it to save.
Suggestions:
indicate more clearly in the instruction what is needed
indicate if one or both fields are mandatory
try to autopopulate as far as possible
try to come up with a default option that will work
First something like "Unable to save because of unknown entity" or some such thing, which doesn't tell me what to do to fix it.
Then the error message in the screenshot included here.
How can we make it easier for users? Can we autopopulate the path based on their github account, at least with the ?
These are the values I tried to use:

This is my github user name, and I said yes to creating the repo and the file when prompted. Then I got the permissions message.
I also tried just putting my username in the top box, thus


Then I got the entity error
THEN, I went to my account, and copied the path from the url and put it in, thus:

I said yes to creating a repo (even though the repo already existed) and got this new and not very helpful error message:
Finally I input this:
And I confirmed that I wanted to save to an existing repository and that I wanted to save the file. And it finally worked.
The text was updated successfully, but these errors were encountered: