-
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
merge from main #53
merge from main #53
Conversation
Checkly implementation
Checkly CI/CD refinement
logging variables earlier on, making sure we see this action occur.
checkly failsafe continued work.
updating set env variables job so I can understand what's causing env…
ref was coming back not as a ref/branch/something, but just as one word.
updated fail safe to create env variables properly.
updated against was referencing an old variable on line 104
added timeout to preview test yml.
removed summary, testing on prod is happening :)
had to adjust the github.ref. to just "main"
updated config to reference repoUrl & tag within checkly ui.
Checkly implementation
Checkly implementation
Checkly implementation
Storage state workaround
updated checkly version
Multi step updates
Multi step updates
initial instrumentation of otel.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
7715459 | Triggered | Slack Webhook URL | 47009ab | next-webstore/checks/resources/alertChannels.ts | 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.
No description provided.