[Feature]: Ability to generate the STL from an exported CSV of the user's contributions

[savager]

Description

I'm unable to target a user on my team even though I specify them. Assume this may be related to an enterprise account?

No target user specified, using authenticated user

But I am able to see their contributions and export a CSV.

Requirements

CLI option to specify a Github generated CSV as the input.

Definition of Done

• CLI option to load a CSV
• Relevant documentation is updated
• Unit tests are updated/written and passing

Additional Notes

No response

[chrisreddington]

Hey @savager, thanks for your interest in gh-skyline and for raising this feature request 🙏

Have you seen #16 ? A similar request was made, and we were able to find some configuration options that allowed them to generate a Skyline for the user's private contributions in their organization. I'll log a separate issue to track the need to document those configuration options 😄 But I wanted to start there and check if that helps?

[chrisreddington]

Hey @savager, just wanted to follow-up on ☝ and see if that resolved the issue? Thank you!

[savager]

Hi, thanks for the response. I didn't get the notification, sorry about that. Will be sure to review your recommendation and close this request. Thanks again

[syahputraarga307-glitch8]

Description

I'm unable to target a user on my team even though I specify them. Assume this may be related to an enterprise account?

No target user specified, using authenticated user

But I am able to see their contributions and export a CSV.

Requirements

CLI option to specify a Github generated CSV as the input.

Definition of Done

• CLI option to load a CSV[ ] Relevant documentation is updated[ ] Unit tests are updated/written and passing

Additional Notes

No response

[AliyuSidi3808]

codeql database create codeql_dbs/dealii_db --language=cpp --source-root=repos/dealii/ --build-mode=none --threads=7 --ram=6000

[Yash-xoxo]

This is a valuable feature for enterprise users and those with private contributions! Here are some thoughts on implementation:

CSV Format Specification:
The GitHub contributions CSV export typically has this structure:

date,count
2024-01-01,5
2024-01-02,0
2024-01-03,12

You'll want to document the expected format clearly, including:

• Required columns (date, count/contributions)
• Date format (YYYY-MM-DD recommended)
• Whether headers are required
• How to handle missing dates (fill with 0 or skip?)

Implementation Approaches:

Option 1: CLI Flag

gh-skyline --csv ./my-contributions.csv --year 2024

Option 2: Interactive Mode

gh-skyline
# Prompts:
# - Username (leave empty for CSV mode)
# - CSV file path (if username empty)

Option 3: Auto-detect

gh-skyline username  # normal mode
gh-skyline ./contributions.csv  # CSV mode (auto-detected)

Privacy & Enterprise Considerations:
This feature is especially useful for:

• Private/enterprise GitHub accounts where the API might not have access
• Users who want to archive their data independently
• Combining contributions from multiple sources
• Custom contribution tracking systems

Validation Needed:

• Check CSV has valid date ranges for the specified year
• Verify contribution counts are non-negative integers
• Warn if dates are missing or out of sequence
• Handle leap years correctly

Documentation Updates:
Should include:

1. How to export CSV from GitHub (Settings → Account → Export account data)
2. CSV format requirements
3. Example CSV file
4. Comparison of CSV mode vs API mode

Testing Considerations:

• Test with various CSV formats (with/without headers, different delimiters)
• Edge cases: leap years, incomplete years, all-zero contributions
• Ensure generated STL matches API-generated output for same data

This would make gh-skyline much more accessible for enterprise users and those concerned about data portability. Happy to help review a PR if needed!