[nodebb-plugin-github-embed] GitHub Issue Embedding
-
@psychobunny reading the title of the issue you used in your example took 4 attempts to make any sense... kept thinking I was reading words over and over again like a child that reads the same line twice.
-
@a_5mith said:
@psychobunny reading the title of the issue you used in your example took 4 attempts to make any sense... kept thinking I was reading words over and over again like a child that reads the same line twice.
And the best part?
I don't even need it anymore
-
@julian Is it possible to update this plugin to work with private repositories? I have a private forum for a group of developers I am working with to create and indie game and it would great to be able to use this but our repo must be private for obvious reasons.
-
Hi @Chris-Rabuse -- private repositories are hidden behind secure API endpoints that require a client ID and secret to access. You can generate one tied to your account in the GitHub account settings. I use my personal GitHub account, but I believe an organization works too.
It looks something like this:
If you register for an id/secret pair and put it into the GitHub Embed settings, it should allow the plugin to read/show private issues.
Keep in mind that this also means unprivileged users on your forum could also use the short codes to retrieve private issue data, so caveat emptor
-
Updated the plugin again. Now you can reference commit hashes!
Enhanced plugin to also embed commits 路 julianlam/nodebb-plugin-github-embed@8c49fc3
Turns issue numbers (#1234) into dynamic entities in posts - Enhanced plugin to also embed commits 路 julianlam/nodebb-plugin-github-embed@8c49fc3
GitHub (github.com)
-
@julian said:
Updated the plugin again. Now you can reference commit hashes!
Enhanced plugin to also embed commits 路 julianlam/nodebb-plugin-github-embed@8c49fc3
Turns issue numbers (#1234) into dynamic entities in posts - Enhanced plugin to also embed commits 路 julianlam/nodebb-plugin-github-embed@8c49fc3
GitHub (github.com)
Just don't try clicking and dragging the scroll bar.
-
@julian Thought wrt usability of the keyword replacement and refusal to do thereof (ref post #18) - why not take a step similar to how wikis go and tack on a footnote link which would link to the appropriate segment at the bottom of the post.
ex "gh01234" -> "gh01234 [1]"
Best of both worlds. Users can find the actual embed they want to see info for, and you don't get weird voodoo going on.
Also hi.