kpromo should pass environment variables to git

[mrueg]

What happened:

Depending on how you treat this, it could also be a feature request.

Trying to set GIT_COMMITTER_EMAIL and GIT_AUTHOR_EMAIL when calling kpromo

https://git-scm.com/book/en/v2/Git-Internals-Environment-Variables

What you expected to happen:

Author / Committer emails are set based on the kpromo call

How to reproduce it (as minimally and precisely as possible):

GIT_COMMITTER_EMAIL="test@example.com" GIT_AUTHOR_EMAIL="test@example.com" kpromo pr --fork test -i --project your-project --t=my-tag --image="" --digests=""

Anything else we need to know?:

Environment:

• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release): Linux
• Kernel (e.g. uname -a): 6.1
• Others: -

[mrueg]

Looking at the implementation, it seems like this is currently not possible:
https://github.com/kubernetes-sigs/release-sdk/blob/fae7e3e5976dff64dc024580bcb445adad823c5d/git/git.go#L1046-L1050

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[xmudrii]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[mrueg]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[mrueg]

/remove-lifecycle stale