Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Site publishing #75

Open
2 tasks
benbalter opened this issue Jul 28, 2016 · 13 comments
Open
2 tasks

Site publishing #75

benbalter opened this issue Jul 28, 2016 · 13 comments

Comments

@benbalter
Copy link
Contributor

  • Implement backend
  • Ability to commit and push to origin's default branch
@jprinaldi
Copy link

How is this coming along? Any help needed?

And while we wait for this feature, what would be the current best alternatives for achieving this type of functionality?

@benbalter
Copy link
Contributor Author

How is this coming along?

Not yet started. On our long-term wish list.

Any help needed?

Yes please! It'll likely be a matter of creating an HTTP interface to Git (via Ruby), and then implementing it within the client-side app.

And while we wait for this feature, what would be the current best alternatives for achieving this type of functionality?

Use GitHub Desktop (or another Git GUI) or drop into command line and run git add and git push.

@mertkahyaoglu
Copy link
Member

@benbalter I would like to work on this.

The only challenge for me is to authenticate users. I can think of one solution which we ask them to provide their Github token in _config.yml and send push requests with it.

@benbalter
Copy link
Contributor Author

@mertkahyaoglu I'd caution against putting creds in _config.yml, as that's almost always committed to the repo. At the very least, I'd use an environmental variable, but even more simply, I'd just shell out and use git commit and git push, relying on Git's existing credentials to handle the authentication — less work for us!

@mertkahyaoglu mertkahyaoglu self-assigned this Jan 15, 2017
@jekyllbot
Copy link

This issue has been automatically marked as stale because it has not been commented on for at least two months.

The resources of the Jekyll team are limited, and so we are asking for your help.

If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.

This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.

@mertkahyaoglu
Copy link
Member

@jekyllbot I recently started to implement this :trollface:

@jekyllbot jekyllbot removed the stale label Mar 15, 2017
@borisrorsvort
Copy link

@jekyllbot @mertkahyaoglu Not sure it's relevant but this could be of some help https://github.com/benbalter/jekyllbot

@DirtyF
Copy link
Member

DirtyF commented Mar 15, 2017

@mertkahyaoglu ProTip™: you can label issues with pinned or has-pull-request to prevent jekyllbot from staling issues

@mertkahyaoglu
Copy link
Member

Oh, that's great, Thanks @DirtyF

@borisrorsvort I will take a look at it 👍

@fowlie
Copy link

fowlie commented Jun 1, 2017

Any progress on this? Would be really great to have this! 😃

@mertkahyaoglu
Copy link
Member

@fowlie Would love that 👍 I can't find enough time for it these days.

@jrsales
Copy link

jrsales commented Aug 30, 2017

I'm just looking for a way to have a quick commit & push from my server onto my gitlab with a button on the admin interface, so I can reuse that gitlab when I deploy in prod. Does anyone have a quick example of that ? :)

@b-long
Copy link

b-long commented Aug 30, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants