NASA-IMPACT / NASA-IMPACT/veda-docs
Use env vars in examples?
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 10
- Forks
- 16
- Avg merge
- 2d 31m
- Merged PRs (30d)
- 4
Description
I noticed that there are few env vars that are potentially relevant to the examples. Namely:
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 reviewing the examples and the environment variables shown in the attached image. Determine which variables are relevant and where the examples should use them; the work is done when the applicable examples consistently use the appropriate documented environment variables.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- Half a day
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100