max-mapper / max-mapper/requirebin
idea: show forks in UI
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 389
- Forks
- 73
- PR merge metrics
- No merged PRs in 30d
Description
when someone 'save as gist' on another users existing sketch, we save it as a fork of the gist on github.
we should surface these forks and show them in the UI somehow
example:
original: https://gist.github.com/maxogden/cc20dd615f6b703cd9aa
forks: https://gist.github.com/maxogden/cc20dd615f6b703cd9aa/forks
fork 1: http://requirebin.com/?gist=c4543485816a5d1b0a46
fork 2: http://requirebin.com/?gist=5a03c74f7b640a9d504d
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 tracing the existing “save as gist” flow and how gist URLs are loaded into the UI. Use the linked original gist and its forks as examples; done means forks of a saved gist are surfaced in the interface in a defined, usable way.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100