@Makyen That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
A recent change made it no longer necessary to set git config user.name and user.email to run a Smokey instance. (That one contained a mistake, this one fixed it)
I recall @Makyen was interested in this having to set committer information in Git config a few months back, no?
@iBug While I am interested in that, as it make it easier to send commits as another user (e.g. if making edits to the files and testing), what I had mentioned was having to set the GitHub username and password outside of the config file.
Basically, when setting up my instance, I found it necessary to manually set the GitHub username and password for the repo/git in order to have SD GitHub operations not fail. Doing so wasn't/isn't part of the instructions for setting up an instance. I had wanted us to either adjust SD so that setting the username/password in the config file was all that was needed (preferred), or to include steps for setting those in the instructions we have for setting up an instance.
@Makyen One solution for this problem, is that when smokey calls git push, that it should pass a custom "credentials helper", something that can give usernames/password to the remote url on push operations
I flagged an answer to this question as spam; the flag was declined, but a moderator deleted the question minutes later. Here is the body of the now-deleted answer:
No, not at all. I created a platform called Clojurecademy which aims
to teach Clojure programming language(which is a dialect ...
@SmokeDetector ? Why wasn't this detected when it was first posted 8 hours ago. Is this another case of the post being edited into spam during the grace period?