This repository was archived by the owner on Jul 6, 2026. It is now read-only.
Conversation
- Delete 18 more stale files left by main->develop merge: app/admin/** (full tree), app/help/, app/profile/[id]/, and 6 orphan error.tsx/loading.tsx whose page.tsx was already removed. Canonical versions remain in app/(protected)/. - FE-2 (useReducer): refactor ProficienciesStep's three related useState calls (selectedSkills, isExiting, isGoingBack) into a single useReducer with a discriminated-union action type. - FE-5 (Server Actions): add submitQuickFeedback Server Action in app/(protected)/help/actions.ts, wired into the Help page via useActionState. Demonstrates the "use server" boundary and revalidatePath; logs feedback server-side. Lint: 0 errors. Type-check: 0 errors. Dev server boots clean. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Action resolver matches the exact git tag name; aquasecurity/trivy-action publishes tags as v-prefixed (v0.36.0, v0.35.0, ...), not bare (0.36.0). Earlier bump used the bare form and CI failed at action resolution. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…rivy fix: dedupe app/* pages, fix Trivy/Gitleaks, close FE-2/FE-5 gaps
ci: add develop to push + pull_request triggers
…rufflehog auto-detect, actions:read
ci: jest.config TS->JS (drop ts-node), develop triggers, codeql v4, t…
…if artifact instead of GHAS
ci: jest.config TS->JS, develop triggers, trufflehog auto-detect, sar…
…with userid, signalr hardened during negotiation
…rect, Invitation page not found fix
…ugh regardless of how busy the rest of the API is
# Conflicts: # .github/workflows/ci.yml # backend/src/Loopless.Application/Interfaces/IFileStorageService.cs # backend/src/Loopless.Infrastructure/Identity/KeycloakAdminClient.cs # backend/src/Loopless.Infrastructure/Storage/FileStorageService.cs # frontend/client/app/(protected)/messages/page.tsx # frontend/client/components/ui/GettingStartedChecklist.tsx # frontend/client/hooks/useGettingStartedChecklist.ts # frontend/client/jest.config.js
…erlays The overlays referenced a secrets.yaml that never existed, breaking 'kubectl kustomize' builds. Production deploys via the Helm chart (devops/helm/loopless) to namespace project-01; mark the overlays as reference-only for a future self-managed cluster. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The merge of main brought devops/k8s/project-01/{README.md,secret.example.yaml},
whose placeholder connection strings (Password=$DB / Password=__DB__) trip the
SQLServer detector as 'unverified' findings and fail the scan under
--results=verified,unknown. Scope-exclude just those two doc files via
--exclude-paths; all detectors stay active for the rest of the repo.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Enes1998
approved these changes
Jun 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR includes changes towards fixing CI/CD issues when deploying. Before, when
developwas merged tomain, TruffleHog & Trivy Scan fails were seen that didn't allow the two branches to merge.Automatic deployment was considered, but let go since it wouldn't make sense for our developing structure. Our structure consists of changes made to
developbranch with reviewing by the team. If all changes are good with features making sense and complete to our scope, then changes are manually merged tomainwhich then auto-deploys instead.With the current fix, the deploy process shouldn't be an issue for a while.
Related milestone
M4 - DevOps MVP
Type of change
Checklist
What is next?
Merge this branch to main, test if deploy and pipeline work. If issues are found again, report issues to team.