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
editor let me not save my first hard work in github1s.
;)
(github1s said in my own repo: unable to save readonly file)
Said it in the step of saving the unsaved file in Editor and the in this step also by github1s suggested (re)naming the initial name untitled-1.sh
by the way:
I never set a readonly state. Also not in the repo. Readme was edited days ago. The file (with the msg: unable to save readonly file) was initial through input to a blank opened editor.
look at *** screenshot ***
2nd try with github1s:
I called the "last opened Editor" append a line; close - and "wuch!" - appending line leave me to nirwana without message.
may be the contributers added this "read-only on the fly" feature now "to hard":
###250 (comment)
The text was updated successfully, but these errors were encountered:
Thank you and congratulations 🎉 for opening your very first issue in this project. github1s fosters an open and welcoming environment for all our contributors.🌸
Incase you want to claim this issue, please comment down below! We will try to get back to you as soon as we can.👀
Feel free to visit github1s.com. 👩💻 If you have any interesting ideas, just open an issue. We would love to hear you and engage in discussions.
1st try with github1s:
;)
(github1s said in my own repo:
unable to save readonly file
)Said it in the step of saving the unsaved file in Editor and the in this step also by github1s suggested (re)naming the initial name
untitled-1.sh
by the way:
I never set a readonly state. Also not in the repo. Readme was edited days ago. The file (with the msg:
unable to save readonly file
) was initial through input to a blank opened editor.look at *** screenshot ***
2nd try with github1s:
may be the contributers added this "read-only on the fly" feature now "to hard":
###250 (comment)
The text was updated successfully, but these errors were encountered: