Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Figure out how to add work items more conveniently #1
Don't like either one because I have to enter the date manually, figure out the slug, and mess with Markdown.
One approach is:
Would be much nicer to do POSSE to Work & get GH Issues created from that automatically. However I'm not sure two-way sync for this exists just yet :-(.
Another is to not automate the issue linking part since my pain point is just creating that file. I would not mind a separate custom UI with price fields etc although that's a tad bothersome to do.
For the best suggestion I will pay $10.00.
added a commit
Jul 15, 2017
That is quite cool. Is it possible to cross link the issue with the original content?
This would help retain the context wherever you are.
In theory, there should be a way to pass the created URL from the micropub client and pass that in the content for the issue when creating it. Likewise, I'm assuming at this point the json response from silo.pub would contain the issue # and URL that could be passed back as yaml front matter that could be read in the jekyll templates.
There is a Jekyll micropub endpoint that you could probably adapt for the specialized yaml.
The trick would be configuring the silo.pub endpoint as a
Only other way I'd think about automating would be to just use the GitHub API in a rake task or plugin, but to host it on GitHub you'd have to use something like Travis CI or Circle CI to run a plugin/rake task and push back to GitHub. I did that for sending webmentions and getting back the json response which I stored as a
Thanks for the input.
I'm thinking that it'll be hard to improve on GitHub's UX without significant investment. I would like it in the log run, but in the short term need a solution as well.
So begin with PESOS, move towards POSSE.
PESOS approach: "GitHub Issues (silo) --> create & update this repository". Can be done with a WebHook. When receiving a new GitHub issue notification, look for posts in the repository that match the issue URL. Then there are two options: found; not found.
Should be able to create a specification & issue for somebody to implement this; and then refactor until we get to POSSE.
POSSE/long term approach:
How does this sound?