Closed bugoverdose closed 6 months ago
Welcome @bugoverdose!
It looks like this is your first PR to kubernetes-sigs/cli-experimental 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.
You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.
You can also check if kubernetes-sigs/cli-experimental has its own contribution guidelines.
You may want to refer to our testing guide if you run into trouble with your tests not passing.
If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!
Thank you, and welcome to Kubernetes. :smiley:
/hold
Adding a hold as we will wait for the next release to merge this
/lgtm /approve
LGTM! The docs go live as soon as the PR is merged, so we can remove the hold during the next kustomize release. Thanks so much for the change
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: bugoverdose, natasha41575
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@natasha41575 This PR is not merged yet, but I'm thinking about applying the changes to our new doc. Below is the PR I'm working on right now.
This PR is not merged yet, but I'm thinking about applying the changes to our new doc. Below is the PR I'm working on right now.
SGTM. We will almost certainly release your fixes before the new docs site is launched, so feel free to add the changes there.
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the PR is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the PR is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the PR is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closed this PR.
from https://github.com/kubernetes-sigs/kustomize/pull/5263
After fixing a bug regarding the replacements field at kustomize, I'm adding an explanation on the current functionality with a basic example.
cc. @natasha41575