Export gist to personal GitHub account
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 477
- Avg merge
- 6h 13m
- Merged PRs (30d)
- 75
Description
Currently the export to Gist is creating an [anonymous gist](https://help.github.com/articles/about-gists/#anonymous-gists).
If a user is logged into GitHub, the gist would be created in the GitHub account.
Maybe the _Login with GitHub_ functionality can be taken from https://github.com/maputnik/editor/issues/155#issuecomment-342917542 ?
Benefits:
- Directly creating a gist in the own GitHub account. Currently you have to fork the anonymous gist to do so.
- Ability to delete gists not needed/wanted anymore from the web browser. Currently you have to contact the GitHub support to delete an anonymous gist.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the current export-to-Gist entry point and reviewing the linked discussion about Login with GitHub. Determine how authenticated GitHub users can create gists in their own accounts while preserving the existing export behavior. Done means a logged-in user can create and manage a personal gist through the browser.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- api, authentication, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100