How to other git contributors about necessary use of 'npm i'
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
Is there a way to inform other devs with help of git, that they have to use npm i
after specific pull (when new / updated package appear)? Now I have only time consuming npm start
to detect that some staff is missing.
I was thinking about git tags but I didn't find any suitable use case.
Expected behaviour for me is a way to log message (last line):
git pull
...
...
create mode 100644 path/to/downloaded/files
create mode 100644 path/to/downloaded/files
Your branch is ahead of 'origin/develop' by 3 commits.
(use "git push" to publish your local commits)
This commit contains one or more new packages, please use 'npm i'
git
add a comment |
Is there a way to inform other devs with help of git, that they have to use npm i
after specific pull (when new / updated package appear)? Now I have only time consuming npm start
to detect that some staff is missing.
I was thinking about git tags but I didn't find any suitable use case.
Expected behaviour for me is a way to log message (last line):
git pull
...
...
create mode 100644 path/to/downloaded/files
create mode 100644 path/to/downloaded/files
Your branch is ahead of 'origin/develop' by 3 commits.
(use "git push" to publish your local commits)
This commit contains one or more new packages, please use 'npm i'
git
2
See gist.github.com/sindresorhus/7996717
– Kunal Nagpal
Nov 22 '18 at 19:54
add a comment |
Is there a way to inform other devs with help of git, that they have to use npm i
after specific pull (when new / updated package appear)? Now I have only time consuming npm start
to detect that some staff is missing.
I was thinking about git tags but I didn't find any suitable use case.
Expected behaviour for me is a way to log message (last line):
git pull
...
...
create mode 100644 path/to/downloaded/files
create mode 100644 path/to/downloaded/files
Your branch is ahead of 'origin/develop' by 3 commits.
(use "git push" to publish your local commits)
This commit contains one or more new packages, please use 'npm i'
git
Is there a way to inform other devs with help of git, that they have to use npm i
after specific pull (when new / updated package appear)? Now I have only time consuming npm start
to detect that some staff is missing.
I was thinking about git tags but I didn't find any suitable use case.
Expected behaviour for me is a way to log message (last line):
git pull
...
...
create mode 100644 path/to/downloaded/files
create mode 100644 path/to/downloaded/files
Your branch is ahead of 'origin/develop' by 3 commits.
(use "git push" to publish your local commits)
This commit contains one or more new packages, please use 'npm i'
git
git
asked Nov 22 '18 at 11:42
Bogusz MichałowskiBogusz Michałowski
159121
159121
2
See gist.github.com/sindresorhus/7996717
– Kunal Nagpal
Nov 22 '18 at 19:54
add a comment |
2
See gist.github.com/sindresorhus/7996717
– Kunal Nagpal
Nov 22 '18 at 19:54
2
2
See gist.github.com/sindresorhus/7996717
– Kunal Nagpal
Nov 22 '18 at 19:54
See gist.github.com/sindresorhus/7996717
– Kunal Nagpal
Nov 22 '18 at 19:54
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430252%2fhow-to-other-git-contributors-about-necessary-use-of-npm-i%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430252%2fhow-to-other-git-contributors-about-necessary-use-of-npm-i%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
See gist.github.com/sindresorhus/7996717
– Kunal Nagpal
Nov 22 '18 at 19:54