可以儲存到github嗎
我可以在plnkr.co上進行專案儲存到github嗎?
Plnkr是完美的呈現javascript專案,並實現即時協作開發.如果我可以從plnkr.co匯出到github將是非常有幫助的.
這可能嗎?那麼怎麼樣
顯然不是.
您有類似的“同步”請求,例如,ofollow,noindex" target="_blank">issue 28 ,這導致了像 plunk_it 這樣的指令碼.
這個想法是要有:
>您的本地回購中的檔案(可以推送到GitHub)
>一種將這些相同檔案傳送到plunker的方法
plunker的作者提出了這些替代方案:
I can suggest to you three alternative ways of getting your code onto Plunker that may or may not better suit your workflow:
-
Create a POST payload (in the same way you do in [r26D/plunk_id]) and send that to 07002 (or 07003 if you’re feeling adventurous).
That is what is used by the AngularJS documentation (see the Edit button on: 07004). -
Sync your snippets with Gist and then use import links for your users. This would use the same mechanism as most of the current templates on Plunker.
To use, create a form in an iframe whose post body would correspond to the Plunk schema you’ve already discovered and post that iframe to 07005: withtarget="_blank | _self"
. -
Create a new importer schema for directories in a Github repository. This is something I’ve been wanting to add but never got around do.
The way the importers work can be seen in: 07006
Now, the major caveat of all of these proposed approaches is that you would not be able to see a listing of forks from your original code. This may be something you want. In fact, there will soon (read: next few months-ish) be more information on plunk histories. Instead of a single fork_of attribute, there will be a history array or something of the sort.
Also, a second caveat is that when I deploy the discussion pane (see: 07007), none of the proposed approaches would support commenting as comments would only be enabled for saved plunks.
程式碼日誌版權宣告:
翻譯自:http://stackoverflow.com/questions/19615717/can-plunker-save-to-github