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

Blog revamp #3

Closed
Tym17 opened this issue Aug 11, 2018 · 3 comments
Closed

Blog revamp #3

Tym17 opened this issue Aug 11, 2018 · 3 comments
Assignees

Comments

@Tym17
Copy link
Owner

@Tym17 Tym17 commented Aug 11, 2018

Comment here for this Blog Post.

@Tym17 Tym17 self-assigned this Aug 11, 2018
@Tym17 Tym17 closed this Aug 11, 2018
@janderudder
Copy link

@janderudder janderudder commented Aug 16, 2018

It is the very first time I hear about GitHub being used as a comment system !
It's funny how Git became a publishing tool. What would it yield to rewrite this tool with this use case in mind ?

Loading

@Tym17
Copy link
Owner Author

@Tym17 Tym17 commented Aug 17, 2018

Thanks for being the very first person to comment on my blog :) ! I don't think it would need a rewrite to work with this use case but definitely some tweaks here and there to make the process automatic. Git itself and Github provide hooks which are triggered when the user does specific actions. I imagine that one could keep a versioned version on Git and have the latest version auto-published using scripts called by those hooks.

Loading

@janderudder
Copy link

@janderudder janderudder commented Aug 17, 2018

I wonder if the author had envisioned this transformation to a publishing and deploying tool.
You're right, many things can be achieved with the pre and post commit scripts, and other hooks. I actually only know a tiny fraction of Git capabilities. Maybe it could have been slightly simpler in some aspects, regarding deployment and publishing.

Loading

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

Successfully merging a pull request may close this issue.

None yet
2 participants