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

Sem CLI collision with old Sem CLI

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
cli

Research direction

Start with the installation script and inspect how it locates the sem command and determines the expected path. Reproduce a system with an older S1 sem command elsewhere on PATH, then verify installation stops and asks the user to remove it when a collision is found.

Written by the indexing model from the issue text.

Description

The Sem CLI can collide with the S1 sem CLI. To mitigate this, we should check the existence of a sem command that is not in the expected path in the installation script, stop and ask the user to remove the old one.

Dominant language
Go
Stars
31
Forks
20
Avg merge
9h 41m
Merged PRs (30d)
2

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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

All issues in semaphoreci/cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.