opensafely-core / opensafely-core/backend-server

Make it easier to keep secrets.env up to date

Open
#220 0 comments 0 reactions 1 assignee View on GitHub

@madwort is already working on this.

Since Mar 1, 2024.

Dominant language
Shell
Stars
1
Forks
5
Avg merge
1h 36m
Merged PRs (30d)
2

Description

  • on initial setup, we copy in secrets-template.env, but after that we don't do anything
  • it would be good to give some feedback to the user if there are keys missing due to new keys being added to the template but not to the production file

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.