quarto-dev / quarto-dev/quarto-cli
Epic: Ongoing Chores
Open
Nobody has claimed this yet.
epic
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
This is for 1.7:
- Inventory our ongoing exposure to "expiring objects" (specifically, certs and developer accounts)
- Create calendar items
- Get our deno issues in shape, because Deno 2 is right around the corner
- This will trigger more bundling problems, because
deno bundlegoes away in Deno 2
- This will trigger more bundling problems, because
- Dependency refresh automation?
Contributor guide
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
No files, tests, or entry points are named. Start by separating the checklist into the expiring-object inventory, calendar items, Deno 2 bundling concerns, and dependency refresh automation, then locate the project areas for each. Done should mean each item has its own scope, acceptance criteria, and follow-up issue where needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- deno, javascript
- Domain
- devops, security, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100