-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HRN 662 responsibilities #725
Conversation
…le user responsibilities
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## dev #725 +/- ##
==========================================
- Coverage 45.30% 44.56% -0.74%
==========================================
Files 430 441 +11
Lines 7883 8020 +137
Branches 2161 2196 +35
==========================================
+ Hits 3571 3574 +3
- Misses 4312 4446 +134 ☔ View full report in Codecov by Sentry. |
@lorenjohnson fyi, I think this should go in a 5.7 release. Responsibilities needs a bunch of dedicated testing in staging and on mobile and I think it'll be too much to do in one bite with i18n and proposals |
Makes sense. I just created the "HyloApp v5.7.0" and set this PR to that. Might want to keep-up with the merge conflict though before they get too heinous :) |
Do you mind if I add "DRAFT: ..." to the heading, as I think it is still draft yes? ( I went ahead and did that 😅 ) |
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
11948920 | Triggered | Sentry User Auth Token | 33832a0 | ios/sentry.properties | 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 secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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.
@thomasgwatson you removed the "DRAFT:" label, is this ready for review? |
Yes, with a caveat that there still might be some tweaks/changes from final
EVO/NODE changes
…On Wed, 10 Jul 2024 at 13:51, Loren Johnson ***@***.***> wrote:
@thomasgwatson <https://github.com/thomasgwatson> you removed the
"DRAFT:" label, is this ready for review?
—
Reply to this email directly, view it on GitHub
<#725 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHT4ARI4H6ZIZSHUXMMLY3ZLWNDXAVCNFSM6AAAAABJJO7E2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRRGQZTCOJXHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
closes #662