Track changes on `.envs` configuration for prod and pre-prod
Open
Nobody has claimed this yet.
Technical
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
There are passwords on some of the files there, so we'll need to use secrets.
At the moment, only .envs/local is tracked.
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 inspecting the tracked .envs/local configuration and how this repository handles secrets. Determine how prod and pre-prod files should be tracked without committing passwords; done means both configurations are represented safely and local credentials remain secret.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100