---

👋 Hi, I'm mnagingvi

I make small pull requests and issues, one at a time. A typo, a clearer error message, a missing line in the docs, a tiny bug fix. Small changes are easy to review, easy to merge, and they add up.¹

Tip

Got a project that could use a tiny improvement? Open an issue and mention me. Small and specific is my favorite size.

---

🌊 How I work

flowchart LR
    A[🔎 Pick a project] --> B[🪶 Spot one tiny thing]
    B --> C{Issue or PR?}
    C -->|Needs discussion| D[📝 Open an issue]
    C -->|Clear fix| E[🔧 Open a pull request]
    D --> F[💬 Learn from the review]
    E --> F
    F --> A

Loading

And here is what that looks like in git history, many small merges instead of one giant one:

gitGraph
    commit id: "project"
    branch fix-typo
    commit id: "fix typo"
    checkout main
    merge fix-typo
    branch clearer-error
    commit id: "clearer error message"
    checkout main
    merge clearer-error
    branch docs-line
    commit id: "add missing docs line"
    checkout main
    merge docs-line

Loading

The math is simple:

$$ \sum_{i=1}^{n} \text{tiny change}_i ;=; \text{a much better project} $$

---

🪶 What counts as a "tiny change"?

Type	Example	Size
📝 Docs	Fix a broken link or unclear README step	🟢 XS
🐛 Bug	One-line fix with a clear reproduction	🟢 XS
💬 Messages	Make an error message actually helpful	🟢 S
✅ Tests	Add a test for one missing edge case	🟡 S
♿ Accessibility	Add a missing alt text or label	🟢 XS
🧹 Cleanup	Remove one unused import or dead variable	🟢 XS

---

✅ Currently

• Set up my profile and website
• Start making small pull requests
• Make one more tiny change today
• Open a well-written issue
• Get a first PR merged somewhere new

---

🧰 My PR checklist

## What
One sentence describing the single change.

## Why
The problem it solves, with a link to the issue if there is one.

## How to check
1. Step one
2. Step two

- [ ] One change only
- [ ] Docs or tests updated if needed

⌨️ Small habits that keep PRs small

• Press Ctrl + Z on any "while I'm here" refactor
• Use git add -p to stage only the lines that belong to this change
• If the title needs the word "and", split it into two PRs

❓ FAQ

Why such small changes? They get reviewed faster, merged more often, and are easy to revert if something goes wrong.

Do you also take on bigger work? Yes, but I try to break it into a series of small PRs so every step stays reviewable.

Can I suggest a project for you to improve? Please do. Open an issue on any of my repos.

---

📬 Find me

• 🌐 Website: mnagingvi.github.io
• 🐙 GitHub: @mnagingvi

---

Just making small pull requests and issues, one at a time.

Footnotes

1. A swan looks calm on the surface, and the paddling happens quietly underneath. Steady progress beats big rewrites. ↩