Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Using github token as part helm install action

Open
  • Is something wrong?
#184 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, helm
Domain
ci-cd, devops

Research direction

Start by locating where the action declares or warns about GITHUB_TOKEN and how it obtains the Helm version. Check the action's workflows for the expected behavior without that variable; done means a pipeline can install Helm without creating an unused or empty token reference.

Written by the indexing model from the issue text.

Description

Hi,
Would it be possible not to require github token for this action?
We shouldn't create or have an empty reference in our pipelines when not required...

Hi,
Just bumped into that warning

Why is a GITHUB_TOKEN variable required in such step?

Getting helm version is a standard web request that doesn't require any special authentication + I don't require this variable and don't want to add an empty var just to avoid the warning..

Originally posted by @assaf-grth in #96

Dominant language
TypeScript
Stars
193
Forks
78
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/setup-helm

All issues in Azure/setup-helm

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.