Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prevent large .ipynb files from being committed #18

Open
Casperento opened this issue Jan 31, 2025 · 0 comments · May be fixed by #21
Open

Prevent large .ipynb files from being committed #18

Casperento opened this issue Jan 31, 2025 · 0 comments · May be fixed by #21
Assignees

Comments

@Casperento
Copy link
Collaborator

Casperento commented Jan 31, 2025

Currently, .ipynb files can be committed to the repository, leading to large file sizes, unnecessary diffs, and potential merge conflicts. To keep the repository clean, we need a solution that prevents accidental commits of .ipynb files. However, simply adding them to .gitignore is not an option, as contributors need to test the scripts locally—especially since report generation provides a reproducible way to present our research results.

Expected Outcome
A cleaner repository that avoids unnecessary large .ipynb files while still allowing contributors to work with Jupyter notebooks locally for testing and report generation.

@Casperento Casperento added the good first issue Good for newcomers label Jan 31, 2025
@Casperento Casperento changed the title Prevent Large .ipynb Files from Being Committed Prevent large .ipynb files from being committed Jan 31, 2025
@Casperento Casperento removed the good first issue Good for newcomers label Feb 5, 2025
@Casperento Casperento self-assigned this Feb 5, 2025
@Casperento Casperento added the good first issue Good for newcomers label Feb 5, 2025
@Casperento Casperento removed their assignment Feb 5, 2025
@Casperento Casperento removed the good first issue Good for newcomers label Feb 6, 2025
@Casperento Casperento self-assigned this Feb 6, 2025
@Casperento Casperento linked a pull request Feb 6, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant