CSV Input for Feature Triage and Tracking
CIFTT turns your soul-crushing spreadsheets into structured GitHub issues and project entries—because if you’re going to suffer, at least automate it.
It’s Friday afternoon.
You’re almost free. Your brain is halfway out the door, already thinking about nachos or silence or both.
Then it happens. A spreadsheet lands in your inbox with 200 feature requests. Two. Hundred.
Your manager wants them in GitHub. Tracked. Tagged. Assigned. Beautifully sorted into your GitHub Project like some kind of agile wizard.
But GitHub doesn’t let you bulk upload to Projects. You have three options:
- Spend the rest of your day (and soul) copying and pasting until your mouse becomes an extension of your sadness.
- Resign yourself to “just using the spreadsheet” and pretending that's fine (it’s not).
- Or—you know—use CIFTT, feed it that cursed CSV, and go live your life.
CIFTT automates the pain away. It parses your spreadsheet and creates GitHub issues, fills in Projects fields, and gives you back your weekend.
You deserve better. Let the robot do the boring part.
| Feature | Status |
|---|---|
| Create issues in a GitHub repository with basic fields | ✅ Done |
| Update basic fields of existing issues in a GitHub repository | ✅ Done |
| Validate labels and assignees in the CSV before creating/updating | 🛠️ In Progress |
| Set GitHub Project fields when creating or updating issues | 📝 To Do |
| Validate GitHub Project field values in the CSV | 📝 To Do |
| Provide tips and examples to help prepare the CSV | 📝 To Do |
# Clone the repo
git clone https://github.com/hillairet/ciftt.git
cd ciftt
# Run the thing
python ciftt.py input.csv myorg/myrepoYour CSV should include headers like:
title,body,labels,assignees,field_name_1,field_name_2,...
Only the title is necessary to create an issue and therefore only the title column is mandatory.
CIFTT is experimental. Like your last relationship. Use with caution. We’re not responsible for any emotional damage caused by accidental issue spam.