Github Authentication and/or Brew Storage #3350
Replies: 3 comments
-
Given what you have written, maybe gists is the way to go, a few points i'd like to have in mind:
|
Beta Was this translation helpful? Give feedback.
-
I believe that newest always shows as the top and we'd have to go to some effort to not load that version.
They do. As I read it, you cannot unpublic a gist but you can move one from private to public. My assumption was we would leave them private and load them via server API call. If they were public we could load them in the browser though so, I dunno. If we needed the functionality to unpublic one, we'd need to create a new gist and recreate the history, but as a private gist.
Gists are available via the Github UI. They show up as an item on the user menu. They can even use that to peruse previous revisions. |
Beta Was this translation helpful? Give feedback.
-
Bonus feature I discovered today. If you name the file you push into the gist, it shows that on the gist listings instead of the gistid. By naming the file the edited I made it very easy to find on the gist listing if I needed to. |
Beta Was this translation helpful? Give feedback.
-
This is a general feature thread about the desirability of three features for homebrewery.
A. Add Github as an authentication system as we do with Google Auth
B. Add a system for storing a Github OAuth token for use with github.
There are two main differences between 2 and 3. The first is that a gist is functionally a git repository with all that goes with that. Creating gists is functionally the same as if step 2 created a new repository for each brew, except for the simplified user interface ( which the users might not even touch )
Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions