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
Hi @thomiceli. First of, thanks a lot for creating this wonderful and useful piece of software! Today I spent a bit of time to try to make use of initializing gists via git push (documented here) which generally works well. To make scripting a bit easier, it would be great if the
git push -u origin master
could somehow be wrapped into an API-call so that it actually returns the newly created Gist-url; Currently the created url (together with further instructions) is only printed in the output.
remote: Your new repository has been created here: {opengist.url}/{id}
remote: If you want to keep working with your gist, you could set the remote URL via:
remote: git remote set-url origin {opengist.url}/{id}
If there was any way to get the {id} after the push-command or by allowing to set {id} directly by allowing something like
git remote add origin {opengist.url}/{id}/init
it would be much easier to automate the process of batch-importing.
The text was updated successfully, but these errors were encountered:
Hi @thomiceli. First of, thanks a lot for creating this wonderful and useful piece of software! Today I spent a bit of time to try to make use of initializing gists via git push (documented here) which generally works well. To make scripting a bit easier, it would be great if the
could somehow be wrapped into an API-call so that it actually returns the newly created Gist-url; Currently the created url (together with further instructions) is only printed in the output.
If there was any way to get the {id} after the push-command or by allowing to set {id} directly by allowing something like
it would be much easier to automate the process of batch-importing.
The text was updated successfully, but these errors were encountered: