Skip to content
This repository has been archived by the owner on Feb 24, 2023. It is now read-only.

Risk: Remove commit messages from being stored in the database. #100

Open
TylerB890 opened this issue Dec 9, 2021 · 0 comments
Open

Risk: Remove commit messages from being stored in the database. #100

TylerB890 opened this issue Dec 9, 2021 · 0 comments
Labels
backend backend, api work risk Security, data privacy, availability, compliance, etc.

Comments

@TylerB890
Copy link
Contributor

Topic
Commit messages are currently stored in the database but are not being used, creating an unnecessary data risk.

Service
Backend

Steps

  • Remove from SQLModels
  • Update GitHub converts to not populate this field
  • Update tests to pass with new schemas and responses
@TylerB890 TylerB890 added risk Security, data privacy, availability, compliance, etc. backend backend, api work labels Dec 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backend backend, api work risk Security, data privacy, availability, compliance, etc.
Projects
None yet
Development

No branches or pull requests

1 participant