Concept
1. Why GitHub (and its limits)
- A free, professional link:
github.com/yourname/hr-attrition-analysis. - README files render as nice pages with images and tables.
- Recruiters for analyst roles recognise it.
- Limit: GitHub doesn't preview .xlsx files — visitors must download them. That's why the README with screenshots and a PDF matters (Lesson 2).
Alternatives/complements: a Google Drive/OneDrive folder with view-only links, a Notion page, or a simple personal site. GitHub is still the most portable.
2. Set up (one time)
- Sign up at github.com with a professional username (
firstname-lastname, notxyz_gamer99). - Profile: photo, name, "Data/MIS Analyst · Excel · Power Query", city, LinkedIn link.
3. Create a repository per project
+ (top right) → New repository:
- Name:
hr-attrition-analysis(lowercase, hyphens) - Description: "Excel analysis of 650 employee records — attrition drivers and recommendations"
- Public
- Tick Add a README file
- Create.
4. Upload files (no Git commands needed)
In the repository → Add file → Upload files → drag the workbook, PDF, data/ and images/ folders → write a commit message ("Add workbook, dashboard images and data") → Commit changes.
Browser uploads allow files up to 25 MiB each; GitHub blocks files over 100 MiB. Keep workbooks small (Dashboards track Module 8 — trim, .xlsb, data model).
5. Edit the README in the browser
Click README.md → pencil icon → paste your template from Lesson 2 → Preview → Commit. Images are referenced by relative path:
Check that every image appears in the rendered page.
6. Make it look finished
- About (gear icon next to About): description, topics (
excel,power-query,dashboard,data-analysis), website link if any. - Releases are optional; a clear README is enough.
- Add a short LICENSE (e.g. MIT) if you're happy for others to reuse your workbook; mention dataset source/licence in the README.
7. Profile README — your portfolio home page
Create a repository named exactly your username (e.g. divyesh-k/divyesh-k) with a README — GitHub shows it on your profile. Example:
# Hi, I'm Divyesh — MIS & Data Analyst (Excel)
I turn messy business data into clean reports and dashboards.
## Projects
| Project | What it shows |
|---|---|
| [Retail Sales Dashboard](https://github.com/divyesh-k/retail-sales-dashboard) | Power Query, Data Model, KPI cards, YoY vs target |
| [HR Attrition Analysis](https://github.com/divyesh-k/hr-attrition-analysis) | cleaning, pivots, attrition drivers |
| [E-commerce Funnel](https://github.com/divyesh-k/ecom-funnel) | funnel chart, conversion by channel & device |
**Skills:** Excel · Power Query · Power Pivot/DAX · Pivot tables · Dashboards · VBA basics
**Contact:** linkedin.com/in/divyesh-k
Then pin your best 3–6 repositories on your profile (Customize your pins).
8. Keep it alive
Update a project when you learn something new (commit message "Add YoY measures and target gauge"). A recent update date and clear commit history show steady work.
9. Optional: for the curious
If you later learn Git: clone the repo, commit locally, push. You can also export Power Query M code and VBA modules as text files next to the workbook so changes are readable (Dashboards track Module 8).
Common mistakes
One giant "excel-projects" repo with no READMEs. Images that don't render (wrong path or capital letters mismatch — paths are case-sensitive). Uploading confidential data. Unprofessional usernames.