Rationale
Investigate the use of git hooks for preventing committing sensitive data. Specifically, pre-receive hooks might be used for this case:
This might be carried out by creating regex rules for any sensitive data within such hooks.
Summary of above:
- Investigate different types of sensitive data which we want to prevent
- Investigate how git hooks can be used to prevent a developer from pushing sensitive data to a repository
- Create the required scripts for preventing the inclusion of all types of sensitive data
- Create a proof-of-concept on a dummy repository to confirm the investigation
For ticket closure
If the outcome of the investigation is successful, we should have a clear plan for using git hooks to prevent sensitive data from being pushed to the repository. This would ideally be paired with a proof-of-concept on a dummy repo.
Rationale
Investigate the use of git hooks for preventing committing sensitive data. Specifically, pre-receive hooks might be used for this case:
This might be carried out by creating regex rules for any sensitive data within such hooks.
Summary of above:
For ticket closure
If the outcome of the investigation is successful, we should have a clear plan for using git hooks to prevent sensitive data from being pushed to the repository. This would ideally be paired with a proof-of-concept on a dummy repo.