-
Notifications
You must be signed in to change notification settings - Fork 32
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] contributor: npm install not always run after PULL #1447
Closed
2 tasks done
Labels
Milestone
Comments
JoernBerkefeld
added
bug
Something isn't working
contributor
improvements for contributing to mcdev
labels
Jul 15, 2024
JoernBerkefeld
added a commit
that referenced
this issue
Jul 15, 2024
… i if multiple commits will be downloaded by PULL
4 tasks
Closed by #1450. |
maybe we can store the previous HEAD's hash key in an environment variable and retrieve that during post-merge? |
JoernBerkefeld
added a commit
that referenced
this issue
Jul 18, 2024
4 tasks
Closed by #1468. |
4 tasks
JoernBerkefeld
added a commit
that referenced
this issue
Jul 22, 2024
JoernBerkefeld
added a commit
that referenced
this issue
Jul 22, 2024
JoernBerkefeld
added a commit
that referenced
this issue
Jul 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current Behavior
it compares the latest commit with the commit before that - but on pull this might include more than one commit
now:
HEAD^1 HEAD
Expected Behavior
we should be using the same logic that is used in post-checkout
then
$NEWHEAD $OLDHEAD
or$1 $2
respectivelySteps To Reproduce
it will not execute npm install because it only compares the last 2 commits with each other, where the last one is the merge commit and the one before that is the latest commit to the feature branch
Version
7.0.4
Environment
Participation
Additional comments
No response
The text was updated successfully, but these errors were encountered: