Skip to content

Conversation

@jmagak
Copy link
Member

@jmagak jmagak commented Feb 27, 2025

IMPORTANT: Do Not Merge - To be merged by Docs Team Only

Version(s): main, 1.4, 1.5

Add the relevant labels to the Pull Request.
Issue: https://issues.redhat.com/browse/RHIDP-6130

Preview links:

2.2. Configuring an external PostgreSQL instance using the Helm Chart

1.3. Installing dynamic plugins in an air-gapped environment

2.3.3. Loading a plugin packaged as a JavaScript package

@rhdh-bot
Copy link
Collaborator

rhdh-bot commented Feb 27, 2025

@jmagak jmagak requested a review from gazarenkov February 27, 2025 17:30
@jmagak jmagak force-pushed the RHIDP-6130-Update-docs-to-refer-to-new-secret-name.1.5 branch from 4a9db79 to 97443be Compare February 28, 2025 12:46
@jmagak jmagak force-pushed the RHIDP-6130-Update-docs-to-refer-to-new-secret-name.1.5 branch from 97443be to 87844d3 Compare March 6, 2025 12:54
@jmagak jmagak force-pushed the RHIDP-6130-Update-docs-to-refer-to-new-secret-name.1.5 branch from 87844d3 to 97efbfe Compare March 6, 2025 14:12
@jmagak jmagak force-pushed the RHIDP-6130-Update-docs-to-refer-to-new-secret-name.1.5 branch from 97efbfe to 52e4ece Compare March 10, 2025 10:52
@jmagak jmagak requested a review from rm3l March 10, 2025 17:30
GitHub Actions added 2 commits March 10, 2025 19:04
RHIDP-6130 Update docs to refer to new secret name

RHIDP-6130 Update docs to refer to new secret name
@jmagak jmagak force-pushed the RHIDP-6130-Update-docs-to-refer-to-new-secret-name.1.5 branch from d6871d6 to d2594c0 Compare March 10, 2025 18:08
@jmagak jmagak force-pushed the RHIDP-6130-Update-docs-to-refer-to-new-secret-name.1.5 branch from d2594c0 to a044015 Compare March 10, 2025 18:16
@jmagak jmagak force-pushed the RHIDP-6130-Update-docs-to-refer-to-new-secret-name.1.5 branch from a044015 to cdb4687 Compare March 10, 2025 18:17
@jmagak jmagak force-pushed the RHIDP-6130-Update-docs-to-refer-to-new-secret-name.1.5 branch from cdb4687 to 925f7f5 Compare March 10, 2025 18:18
@jmagak jmagak force-pushed the RHIDP-6130-Update-docs-to-refer-to-new-secret-name.1.5 branch from 925f7f5 to d2594c0 Compare March 10, 2025 18:23
@jmagak jmagak requested a review from rm3l March 11, 2025 08:48
@rm3l
Copy link
Member

rm3l commented Mar 11, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Mar 11, 2025
@jmagak jmagak added Technical review done ⛅ Any procedure has been succesfully tested and removed Technical review needed 🔩 Test all the procedures labels Mar 11, 2025
@jmagak jmagak requested a review from hmanwani-rh March 11, 2025 09:38
@themr0c themr0c merged commit d149296 into redhat-developer:main Mar 13, 2025
3 checks passed
@themr0c
Copy link
Member

themr0c commented Mar 13, 2025

/cherry-pick release-1.4

@themr0c
Copy link
Member

themr0c commented Mar 13, 2025

/cherry-pick release-1.5

@openshift-cherrypick-robot
Copy link
Contributor

@themr0c: #962 failed to apply on top of branch "release-1.4":

Applying: Update docs to refer to new secret name
Using index info to reconstruct a base tree...
M	modules/configuring-external-databases/proc-configuring-postgresql-instance-using-helm.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/configuring-external-databases/proc-configuring-postgresql-instance-using-helm.adoc
CONFLICT (content): Merge conflict in modules/configuring-external-databases/proc-configuring-postgresql-instance-using-helm.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Update docs to refer to new secret name

In response to this:

/cherry-pick release-1.4

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot
Copy link
Contributor

@themr0c: new pull request created: #985

In response to this:

/cherry-pick release-1.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

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.

6 participants