-
Notifications
You must be signed in to change notification settings - Fork 0
Hotfix/ci cd pipeline fix #75
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
Conversation
- Clean up inconsistent tags from previous mixed strategy - Modify ci-02-pipeline.yml to use app-specific tags (blog-v*, api-v*, web-v*) - Skip versioning for apps without changes - Update ci-04-release.yml for independent app coordination - Global releases (v*) track which app versions are included - Each app maintains its own SEMVER independently - Apps without changes don't get new versions 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
…ive design - Fixed branch dropdown with truly fixed width (140px/120px/100px responsive) - Restored working navigation structure with numbered sections - Created professional landing page with clear section access - Added comprehensive .pages navigation files for all sections - Fixed all broken links in WIKI.md with proper relative paths - Enhanced CSS with professional styling, progress bar, and back-to-top - Added advanced JavaScript functionality and keyboard shortcuts - Removed cookie consent and simplified configuration - Professional Material Design theme with Inter/JetBrains Mono fonts - Mobile-optimized responsive design with proper breakpoints 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
- Merged AUTOMATION.md automation tasks into HOW-TO as new section - Integrated WIKI.md navigation references into HOW-TO - Updated README.md to make HOW-TO the main documentation entry point - Reduced docs folder from 10 to 8 files (20% reduction) - HOW-TO now serves as comprehensive entry point for quick references 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 20776767 | Triggered | Generic High Entropy Secret | fab2245 | infra/traefik/.env.example | View secret |
| 20387822 | Triggered | SMTP credentials | 0775530 | apps/n8n/README.md | 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.
Fix issue #72