Avoid tracking PDF result files in the main github draft repository
Open
Nobody has claimed this yet.
decision-required
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
From #3313 :
Separately, we should consider not tracking all the papers in the primary git repository; source checkouts of the draft are huge and growing rapidly due to this.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked context in #3313 and inspect how PDF result files and papers are tracked in the primary draft repository. Determine which generated outputs are currently committed and define done as keeping those results out of the main repository without removing the draft sources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, tex
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100