A resume written from what you put on GitHub
GitHubPrint reads your public repositories, READMEs and your own resume repository, then lays them out as an A4 document. Every line can be traced back to where it came from on GitHub.
Sign in to start. Save as PDF, Word or HTML.
Alex Morgan
Developer building web interfaces
github.com/example
Builds document-style web tools with Next.js and TypeScript. Each project ships with a README and a link to the result.
Taken from your READMEs and profile bio
Selected projects
A web app that turns GitHub work into A4 documents
Components for checking screen drafts quickly
Repositories pinned to your profile
Technologies
Only tools found in files across two or more repositories
Experience
Exactly as you wrote it in your resume repository
How it works
Sign in with GitHub
Your public repositories are loaded. Private repositories are read only if you pick them.
Pick a template and sources
Choose one of four templates depending on who will read the document.
Review and save
Read it on screen, then save it as a PDF, Word or HTML file.
Four documents for four kinds of reader
The same GitHub history needs a different shape for a first introduction than for a detailed review.
Brief
Your stack and selected projects, ready for a first introduction.
For a recruiter you are contacting for the first time
Profile
A portfolio that puts the projects you built first.
For an interviewer who wants to see projects
Insight
A report on recurring technical choices and work patterns.
For a peer reviewing how you work
Resume
Your own experience and projects in a considered resume.
As the formal resume attached to an application
Only what GitHub shows
Documents are built from public evidence. A claim without evidence stays out, however good it would sound.
What goes in
- Your profile and public repositories
- READMEs, topics, stars and recent updates
- Homepage and deployment links
- Root files such as package.json, and recent commit messages
- Experience and contact details you wrote in your resume repository
What stays out
- Years of experience
- Judgements about leadership or teamwork
- Company revenue or business results
- Rankings or scores against other developers
A README that wasn't found is not reported as missing, and a test setup is not reported as passing tests.
Save it the way you need it
PDF and HTML keep the layout you see on screen. Word gives you a file you can keep editing.
- PDF.pdf
- Send & submit
- Keep the page layout for applications and attachments.
- Word.docx
- Edit & collaborate
- Revise and collaborate in Word or Google Docs.
- HTML.html
- Read in a browser
- Open and print the same template in a browser.
Questions about creating GitHub documents
What can I create with GitHubPrint?
Create a Brief introduction, a Profile portfolio, an Insight activity report, or an authored Resume. All four formats support Korean and English, with PDF, editable Word, and portable HTML exports.
Does every template require a resume repository?
Only Resume requires a resume repository and resume.yaml. Brief, Profile, and Insight use your GitHub profile and project information to compose the document.
Can I download examples without signing in?
The example preview lets you try PDF, Word, and HTML downloads without signing in. Examples use fictional data. Creating a document from your own account requires GitHub sign-in.
Can I edit the file in Google Docs?
Upload the downloaded .docx file to Google Docs and open it there. Font choices and pagination can vary between editors.
Will my result appear in search engines?
Signed-in result pages are configured to be excluded from search indexing. The public resume showcase contains separately published content and is distinct from personal result pages.