github action interactive()
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 65
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Consider a mode of functionality where the nice hex grid is part of a Quarto or Rmarkdown document that is generated on a schedule or github action, automatically and without a console. Kaggle works this way. Some academic reporting. Many docs in a business context.
`utils::menu()` would only be triggered if `interactive()` is TRUE
For an example of how `interactive()` is used in another context, Colin Gillespie writes here on making a better r_profile
https://www.jumpingrivers.com/blog/customising-your-rprofile/
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 tracing where utils::menu() is called and how interactive() is currently checked. Reproduce the behavior in a scheduled GitHub Action or generated Quarto/R Markdown document, then define the non-console behavior and verify that console use remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- cli, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100