mateogianolio / issuance Goto Github PK

bacause anyone can open an issue maybe a better option will be only allow displaying issues with the label blog since only repo ownwers can assign labels?

Is step 3 optional?
Should't lib/globals.js be in .gitignore since it contain my token?
Also, can you add another step that tells me what to do after I pushed to gh-pages branch?

blah

Images, that show up normaly in the issues, are not displayed in the blog.

Hi Mateo, which License this project uses?

blabla

It would be cool to see a version of this that leveraged the ability to put notes in a GitHub release as the actual content for a "post", and have issues -- those created by other users at least -- moved to a separate section called Q&A, à la Tumblr.

testing

Intro into love2d
in love2d, tutorial,
by egordorichev, 5/1/2017

That comma, after tutorial, is superfluous

Does this appear on the blog too?

the no-scope personal access token still grants read-only access to private repos. I tested using just "x" as my token and it works just fine since github's api is read-only by default for public repos. Maybe test out some different scenarios to see if this is true. if it is, remove the token requirement from your documentation and hard-code the token to "x" as I have done.

here's my sample using "x" as the token:
https://dmidlo.github.io/blog/

• open it up in devtools, look at elements > head > script
• My token is assigned to the const TOKEN

This is a Github issue rendered as a blog post.

Setting up your own blog is pretty straightforward:

1. Fork this repository.
2. Create a Github personal access token with no scope.
3. Open js/globals.js and change USERNAME to your username and TOKEN to the token you just created.

Link to individual posts by appending ?<issue_number> to index.html.

How is that useful?

textextext

a test

Example issue body, rendered with marked.

1. List item
2. List item
3. List item

Code block

{
  const a = 2;
  const b = 2;
  return a * b;
}