The person who knew why left. Now what?
With SharedSource, the reason lives in a shared Markdown file.
By joining the waitlist, you agree to our Terms of Service and Privacy Policy.
The real cost
Every week, SWEs burn hours hunting down why a piece of code was written. The answer's there: it's just scattered in someone's head or an outdated wiki.
How SharedSource actually works
1
Merge PRs like you always do.
2
When it matters, SharedSource drafts an update in a companion PR.
3
Merge it, edit it, or close it — you decide.
4
The Markdown file stays current. Use it.
Why now
I'm a high school senior. Over the summer, I listened to SWEs, heard the pain, and shipped a fix. Let's make SharedSource earn its place in your workflow.
By joining the waitlist, you agree to our Terms of Service and Privacy Policy.