ddsjoberg/gtsummary
View on GitHubHow to reduce the size of the repo....it's gotten rather large.
Open
#1736 opened on Jun 12, 2024
2 comments (2 comments)0 reactions (0 reactions)0 assignees (0 assignees)R1,188 stars (1,188 stars)145 forks (145 forks)batch import
help wanted
Description
This issue does not include a description.
Contributor guide
- Tech stack
- None
- Domain
- devops
- Issue type
- chore
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 2
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- half day
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- unclear
- Prerequisites
- Familiarity with GitUnderstanding of R package structureKnowledge of repo size analysis tools
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 20
- Research direction
- First, analyze the repository size using Git commands like `git rev list objects all` combined with `git cat file` to find large objects. Check the R package structure for large data files, images, or vignettes. Consider using Git LFS for large files or removing unnecessary files. Also review the .gitignore and .Rbuildignore to exclude large artifacts. The maintainer (ddsjoberg) should clarify which files are candidates for removal or if a history rewrite is acceptable.