Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Helm instructions not available #236

Closed
RSijelmass opened this issue Dec 22, 2019 · 2 comments · Fixed by #237
Closed

[BUG] Helm instructions not available #236

RSijelmass opened this issue Dec 22, 2019 · 2 comments · Fixed by #237
Labels
bug Something isn't working

Comments

@RSijelmass
Copy link

RSijelmass commented Dec 22, 2019

Describe the bug
For any new contributors, the CONTRIBUTING.md file goes through a detailed step-by-step to get the project set up on everyone's local machine. One can decide to run the project locally, or through docker. In the latter, however, a reference is made to the README.md on how to use helm.

This, however, seems to be removed. The link is also referencing to a header #using-helm, which does not exist in the README. Now the docker setup can't easily be completed by anyone joining the project.

To Reproduce

  1. Go to CONTRIBUTING.md
  2. pass through to the link provided.
  3. Notice the lack of information given

Expected behavior
Either add the setup and complete usage of helm directly on the CONTRIBUTING.md, or reinstate it in the README.md.

@RSijelmass RSijelmass added the bug Something isn't working label Dec 22, 2019
@PrasadG193
Copy link
Collaborator

Hi @RSijelmass,
Thanks for reporting this. The instructions in CONTRIBUTING.md seem to be outdated. I'll update it ASAP.

@PrasadG193
Copy link
Collaborator

Hey @RSijelmass ,
We have updated the CONTRIBUTING.md as per the latest changes. Please let us know if you still face any issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants