shift-org / shift-org/shift-docs
abstract settings from codebase and replace with git-safe placeholders that don't match prod
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 25
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
move node env vars and other settings out into a config file that won't be stored in git or anyway won't have values stored in git, cf https://shift2bikes.slack.com/archives/CCFLDTCF7/p1709920533388469?thread_ts=1709871971.848139&cid=CCFLDTCF7
I think @ionous is already working on this here: https://github.com/shift-org/shift-docs/pull/628
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 pull request 628 and the referenced discussion, then identify the Node environment variables and other settings currently stored in the codebase. Done means settings are loaded from a configuration source that is not stored in git, with placeholders that cannot match production values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100