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

CLI requires $HOME variable

Open
  • Is something wrong?
#44 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 8 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
cli, operating-systems

Research direction

Start by locating the CLI code that reads the $HOME environment variable and produces the reported home-directory error. Reproduce the failure with $HOME unset, then verify that pangolin-cli starts successfully in that environment without breaking normal startup behavior.

Written by the indexing model from the issue text.

Description

needs investigating
Describe the Bug

CLI failed to start if $HOME environment variable is not set:

[pangolin-cli] failed to get home directory: $HOME is not defined

OLM don't have such problem.

Environment
  • Client Version: 0.5.1
To Reproduce

Unset $HOME environment before pangolin-cli call.

Expected Behavior

Machine like environments must not have dependency on $HOME.

Dominant language
Go
Stars
50
Forks
18
Avg merge
2d 18h
Merged PRs (30d)
6

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 fosrl/cli

All issues in fosrl/cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.