Investigate HAVE_HASH_BANG_EXEC induced git bug

Open
#42 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
bash, git
Domain
cli

Research direction

Start by reproducing the regression in the Git test cases and tracing the HAVE_HASH_BANG_EXEC change. Compare behavior before and after the reverted change; done means identifying a fix that preserves the Git tests without reintroducing the regression.

Written by the indexing model from the issue text.

Description

I have reverted the change to unset HAVE_HASH_BANG_EXEC because it caused a regression in the Git test cases.

We will need a fix that does not regress Git.

Dominant language
Groovy
Stars
12
Forks
7
No merged PRs in 30d

Contributor guide

Open the 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 zopencommunity/bashport

All issues in zopencommunity/bashport

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.