My Workflow Headless CMS using Hugo, Github Issues and Github Actions.
Every time a new issue is created, a new post is created as well.
main branch holds the content in markdown format. See folder gh-pages branch contains the distributable html site. Submission Category: Maintainer Must-Haves & DIY Deployments
Yaml File or Link to Code {% github https://github.com/oscarnevarezleal/gh-cms %}
Additional Resources / Info live demo
Create a new post by submitting a new issue
ja das stimmt das war ein sehr schönes erlebnis und das hat mich auch gefreut und das ist ja das was wir jetzt haben das war ja schon immer sehr gut für mich aber das war auch sehr wichtig und
juujbb
Firstly, this is pretty cool my friend - thanks for sharing! I will have to play around with this on my developer blog and portfolio GitPages SSG site repo which is based on Jekyll and GitActions…
One suggestion did occur to me however, and I am curious to hear what you and other members of the dev community think…
Rather than firing your actions workflow job in response to the on-issue event - why not trigger based on new Discussions / Comments on Discussions and leave the issue tracking feature as is to be used for code base issue tracking?
Hello!
I hope you are doing well!
We are a security research team. Our tool automatically detected a vulnerability in this repository. We want to disclose it responsibly. GitHub has a feature called Private vulnerability reporting, which enables security research to privately disclose a vulnerability. Unfortunately, it is not enabled for this repository.
Can you enable it, so that we can report it?
Thanks in advance!
PS: you can read about how to enable private vulnerability reporting here: https://docs.
Mora valvas mallem inambitiosa tuam sed voce Canaeque aratro isto ab opportuna lacerare Anienis Lorem markdownum terrigenae genu videtur, fando lucos nigris, curvantur. Condidit nostra serpentis possis de videar Curibus caput petunt parentis faciendus conataque lente Saturnius.
Fronte et adeo Iovi intravit Sorores esse corpora otia interea Thebis amnesque Disiectisque ego ora obscurus, vias gemitu, ad quos, aras messoris et oculos derat: votique habuisse legit. Ubi manu, non vixque Bacchus, modo tristique inque et arte fitque ultimus, cumulusque aestibus caede.
Loving him is like Driving a new Maserati down a dead-end street Faster than the wind, passionate as sin Ending so suddenly Loving him is like trying to change your mind Once you’re already flying through the free fall Like the colors in autumn, so bright Just before they lose it all
Losing him was blue like I’d never known Missing him was dark gray, all alone Forgetting him was like Trying to know somebody you never met But loving him was red
Hi,
I found a potential vulnerability in this project. Can you draft Security Advisories and invite me in to further disclose and discuss the vulnerability details and potential fix?
Thanks!
I’m curious as to why you chose to use this blogging platform. Is it because the custom layouts are easier or more flexible compared to the templates on Blogger.com? Or is it because of the larger amount of free space that can be obtained?