luckyframework / luckyframework/website
Docs for built-in ENV vars
Open
Nobody has claimed this yet.
- Dominant language
- Crystal
- Stars
- 39
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
We now use ENV["LUCKY_TASK"], but we also have ENV["LUCKY_ENV"] and some others floating around. Maybe we can throw them all in to a guide or just make sure they're all mentioned...
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 ENV variables named in the issue and the referenced pull request #595. The work is done when the website documents all built-in ENV variables, including LUCKY_TASK and LUCKY_ENV, in a clear guide or existing documentation section.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100