Complex logic ahead...
We have three sets of values, in order of precedence (last wins):
1. The builtin values.yaml defaults
2. The profile the user selects
3. Users input (-f or --set)

Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2).

However, we can workaround this by placing all of (1) under a specific key (.Values.defaults).

                                                                                <input type="hidden" name="name"
                                                                                       value="${f:h(artifact.name)}">
                                                                                <input type="hidden" name="version"

									<label for="requestFile" class="col-sm-3 text-sm-right col-form-label"><la:message
											key="labels.esreq_request_file"
										/></label>
									<div class="col-sm-9">
										<input id="requestFile" type="file" name="requestFile" class="form-control-file" />
									</div>
								</div>
							</div>
							<div class="card-footer">
								<c:if test="${editable}">

title: "x/pkgsite: package removal request for [type path here]"
labels: ["pkgsite/package-removal"]
body:
  - type: markdown
    attributes:
      value: "Please answer these questions before submitting your issue. Thanks!"
  - type: input
    id: package-path
    attributes:
      label: "What is the path of the package that you would like to have removed?"
      description: |
        We can remove packages with a shared path prefix.

                                                        key="labels.backup_bulk_file"/></label>
                                                <div class="mb-2 mr-sm-2"><input type="file" id="bulkFile"
                                                                                 name="bulkFile"
                                                                                 class="form-control-file"/></div>

                                    <div class="col-sm-9">
                                        <la:errors property="attributes.gidNumber"/>
                                        <input type="number" id="attributes.gidNumber" name="attributes.gidNumber" class="form-control"/>
                                    </div>
                                </div>
                            </div>

			<h2>
				<la:message key="labels.system_error_title" />
			</h2>
			<div class="errormessage"><la:message key="labels.contact_site_admin" /></div>
		</div>
	</main>
	<jsp:include page="../footer.jsp" />
	<input type="hidden" id="contextPath" value="<%=request.getContextPath()%>" />
	<script type="text/javascript"
		src="${fe:url('/js/jquery-3.6.3.min.js')}"></script>

			<h2>
				<la:message key="labels.system_error_title" />
			</h2>
			<div class="errormessage"><la:message key="labels.contact_site_admin" /></div>
		</div>
	</main>
	<jsp:include page="../footer.jsp" />
	<input type="hidden" id="contextPath" value="<%=request.getContextPath()%>" />
	<script type="text/javascript"
		src="${fe:url('/js/jquery-3.6.3.min.js')}"></script>

labels: ["pkgsite"]
body:
  - type: markdown
    attributes:
      value: "Please answer these questions before submitting your issue. Thanks!"
  - type: input
    id: url
    attributes:
      label: "What is the URL of the page with the issue?"
    validations:
      required: true
  - type: input
    id: user-agent
    attributes:
      label: "What is your user agent?"

# Usage: Go to
# https://github.com/tensorflow/tensorflow/actions/workflows/release-branch-cherrypick.yml
# and click "Run Workflow." Leave "Use Workflow From" set to "master", then
# input the branch name and paste the cherry-pick commit and click Run. A PR
# will be created.

name: Release Branch Cherrypick
on:
  workflow_dispatch:
    inputs: