Add more advanced docs and testing
Open
Nobody has claimed this yet.
ci
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
- How to do different roll-over strategies for licensing
- Ingress, examples, etc.
- Config practices, string overrides, etc.
- Note about default callback URL for RStudio Workbench...
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. Review the existing documentation structure and locate the sections covering licensing roll-over strategies, ingress examples, configuration and string overrides, and the RStudio Workbench default callback URL. Done means each checklist topic has clear, tested documentation and the issue's testing expectation is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100