quarto-dev / quarto-dev/quarto
git tags (and CI)?
Open
Nobody has claimed this yet.
future
vscode
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
The previous repository for vscode extension (https://github.com/quarto-dev/quarto-vscode) has tags and releases, but they don't seem to be here.
It would be useful to have tags to track updates.
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
Compare the current quarto repository with the previous vscode extension repository at https://github.com/quarto-dev/quarto-vscode, focusing on its tags and releases. Determine how updates should be tagged here and whether CI is part of that workflow; done means the agreed tagging process is established and updates can be tracked through repository tags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100