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

Built-in stash/rebase fixes #1852

Merged
merged 4 commits into from
Sep 27, 2018

Conversation

dscho
Copy link
Member

@dscho dscho commented Sep 27, 2018

Thanks to some battle-testing by adventurous Git for Windows v2.19.0 users, we already discovered a couple of corner cases where the built-in versions did not quite do the job we expected. This PR intends to fix them all ;-)

When converting the `stash apply` command, we were missing at least two
error messages: when the diff could not be applied with `--index`, we
want to suggest to re-run the command without `--index`.

While at it, and because we now can, let's also add an error message in
the case that the diff could not be generated in the first place (the
shell script could not do that, as it piped the output of `git diff` to
`git apply`, and there is no portable way to handle errors in the
command whose output is redirected).

Noticed by Matthew Cheetham.

Signed-off-by: Johannes Schindelin <[email protected]>
@dscho
Copy link
Member Author

dscho commented Sep 27, 2018

cc @ungps re: "fixup! stash: convert apply to builtin"

cc @mjcheetham, too, as he discovered the problem ;-)

…builtin

The `--gpg-sign` option takes an *optional* argument, not a mandatory
one.

This fixes git-for-windows#1836.

Signed-off-by: Johannes Schindelin <[email protected]>
The `--gpg-sign` option takes an *optional* argument, not a mandatory
one.

This was discovered as part of the investigation of
git-for-windows#1836.

Signed-off-by: Johannes Schindelin <[email protected]>
@dscho dscho force-pushed the built-in-stash-rebase-fixes branch 5 times, most recently from cdeb59b to 126235f Compare September 27, 2018 14:08
In Azure Pipelines, a sane setting is to prevent secret variables from
being shared with Pull Requests originating from forks.

In Git, we use such a secret variable: we want to mount a file share on
which previous we store outcomes of previous runs, and avoid re-running
known-good phases (both for speed as well as to avoid spending resources
unnecessarily). This file share should not be mounted in PRs.

Signed-off-by: Johannes Schindelin <[email protected]>
@dscho dscho force-pushed the built-in-stash-rebase-fixes branch 2 times, most recently from 68ba9e7 to fb77ec5 Compare September 27, 2018 16:18
@jamill jamill merged commit a5565b4 into git-for-windows:master Sep 27, 2018
@dscho dscho deleted the built-in-stash-rebase-fixes branch September 27, 2018 20:59
@dscho dscho added this to the v2.19.0(2) milestone Sep 27, 2018
dscho added a commit to git-for-windows/build-extra that referenced this pull request Sep 27, 2018
Several corner case bugs [were
fixed](git-for-windows/git#1852) in the
built-in `rebase`/`stash` commands.

Signed-off-by: Johannes Schindelin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants