Uh oh!
There was an error while loading. Please reload this page.
[C-4465] Update usdc transactional emails - #8744
Conversation
|
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 11648675 | Triggered | Generic High Entropy Secret | 72e7810 | .env | View secret |
| 11648676 | Triggered | Generic High Entropy Secret | 72e7810 | .env | View secret |
| 11648677 | Triggered | Generic High Entropy Secret | 72e7810 | .env | View secret |
| 11648678 | Triggered | Generic High Entropy Secret | 72e7810 | .env | View secret |
| 10116465 | Triggered | Generic High Entropy Secret | 72e7810 | .env | View secret |
| 11648679 | Triggered | Generic High Entropy Secret | 72e7810 | .env | View secret |
| 11648680 | Triggered | Generic High Entropy Secret | 72e7810 | .env | View secret |
| 11648681 | Triggered | Generic High Entropy Secret | 72e7810 | .env | View secret |
| 10116465 | Triggered | Generic High Entropy Secret | e2afc3f | .env | View secret |
| 11648675 | Triggered | Generic High Entropy Secret | e2afc3f | .env | View secret |
| 11648676 | Triggered | Generic High Entropy Secret | e2afc3f | .env | View secret |
| 11648677 | Triggered | Generic High Entropy Secret | e2afc3f | .env | View secret |
| 11648678 | Triggered | Generic High Entropy Secret | e2afc3f | .env | View secret |
| 11648679 | Triggered | Generic High Entropy Secret | e2afc3f | .env | View secret |
| 11648680 | Triggered | Generic High Entropy Secret | e2afc3f | .env | View secret |
| 11648681 | Triggered | Generic High Entropy Secret | e2afc3f | .env | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
| .mobile { | ||
| display: block !important; | ||
| width: auto !important; | ||
| height: auto !important; | ||
| float: none !important; | ||
| } | ||
| .email-container { | ||
| width: 100% !important; |
| name: string | ||
| handle: string | ||
| is_deactivated: boolean | ||
| profile_picture_sizes: string |
There was a problem hiding this comment.
is this a string? I thought this was an object of some sort
DejayJD
left a comment
There was a problem hiding this comment.
LGTM, one note about types tho
[05c268e] add key + bpm fields to discovery track metadata (#8757) Michelle Brier [66aa450] add listens rate limiter with tests (#8786) alecsavvy [32ffd84] add new graph urls (#8795) alecsavvy [d9b4ee3] Add release_date, is_scheduled_release to playlist api (#8790) Reed [667037e] [PAY-2849] Support gated content in Manager Mode (#8746) Randy Schott [c44bfdc] [C-4465] Update usdc transactional emails (#8744) Isaac Solo [fbe5cbe] Add vendor to buyer notification (#8787) Isaac Solo
Description
Update these e-mails for the new design system.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide repro instructions & any configuration.
Ran notifications plugin locally and sent e-mails to myself.