Expose environment into a command template

[konradekk]

hi! nicely done this plugin here of yours!

i’d like to have environment variables passed into the template—i thought i prepare a pr for you to speed up things (discussions, merger, deployment etc.)… i’d happily give more details or amend the pr if needed.

cheers!

[hasezoey]

sorry to ask this, but any news from an maintainer on this PR?

[konradekk]

He apparently shows up from time to time, I guess. But it’s more like once a year or so than every two weeks… So here, it seems we still have roughly ca. half a year. ;)

Be patient or… just fork that! (I did not tested that—so feel free to tell how it went etc.! Thanks in advance for the feedback!)

[hasezoey]

I did not tested that—so feel free to tell how it went etc.! Thanks in advance for the feedback!

for my use-case i just ended up using an command that directly takes an environment variable from the environment (for completing it was semantic-release-rust)

[konradekk]

Neat! I don’t want to invest time in that if it won’t be used—and it seems it won’t as there’s quite a big lag regarding any kind of interaction with the maintainer(s)… 😅

[konradekk]

Is this anyhow needed for anybody? 🤔

[hasezoey]

Is this anyhow needed for anybody? thinking

i am currently not "requiring" this, but this would probably be useful, because currently you either had the wanted program to have environment variables, or required to wrap the command in a script