Skip to content

Conversation

@prkhrkat
Copy link
Contributor

Description

Fixes #

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR requires documentation updates?
  • I've updated documentation as required by this PR.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have tested it for all user roles.
  • I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?


iamayushm and others added 30 commits July 31, 2025 17:04
fix: update default sequence for bulk edit config table and correct README link
…pipelines, add duplicate removal utility, and enhance logging and fallback mechanisms.
…tus fetching, extracting common logic into reusable functions and improving linked pipeline handling.
…nd maintain consistency with refactored CI status handling logic.
…ce readability and align with refactored CI pipeline handling logic.
…r.go` to enhance code clarity and eliminate dead code.
…y and replace the inlined method in `CiHandler.go`.
…nes. Add linked pipeline mapping and workflow statuses, refactor status population logic, and introduce reusable adapter methods for linked CI workflows.
chore: Fix cluster and environment page
chore: Update `authenticator` and `common-lib` dependencies to latest versions.
…ion-specs

chore: add resource recommendation APIs and update openapi.yaml
badal773 and others added 2 commits August 18, 2025 16:54
* added support for cronjob annotations and probes

* support for older charts

* reconfiguring semverCompare

* removed restartPolicy from cronjob-config

* added support for external-secrets.io/v1

* added default values for eso

* older compatibility

* rectify the semverCompare

* added support for jobLabels and jobAnnotations
* feat: api spec hosting mechanism

* fix: trigger condition update on wf file

* fix: remove old wf

* refact in specs

* generate-api-docs.sh fix

---------

Co-authored-by: prakhar katiyar <[email protected]>
Co-authored-by: prakhar katiyar <[email protected]>
@gitguardian
Copy link

gitguardian bot commented Aug 25, 2025

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
19465121 Triggered Generic High Entropy Secret 9b21172 scripts/sql/34304100_bulk_edit_config.up.sql View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. 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


🦉 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.

@bito-code-review
Copy link

Bito Automatic Review Skipped - Large PR

Bito didn't auto-review this change because the pull request exceeded the line limit. No action is needed if you didn't intend for the agent to review it. Otherwise, to manually trigger a review, type /review in a comment and save.

@prkhrkat prkhrkat reopened this Aug 26, 2025
@sonarqubecloud
Copy link

@prkhrkat prkhrkat closed this pull request by merging all changes into develop in d9c6787 Aug 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants