How to get GitHub commit notifications by email after January
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I'm part of several teams that depend heavily on GitHub's convenient "send an email every time anyone pushes commits" service, which is slated to disappear in a few weeks. I'm aware that it's been deprecated in favor of a more general WebHooks mechanism, but the docs are not very clear on exactly how one would instantiate the general mechanism to get back what the existing one does.
What is the easiest way to replicate the functionality that's going away?
github
edited Dec 1 '18 at 14:29
Catalin Hritcu
405411
asked Nov 22 '18 at 0:19
Benjamin PierceBenjamin Pierce
33919
add a comment |
I'm part of several teams that depend heavily on GitHub's convenient "send an email every time anyone pushes commits" service, which is slated to disappear in a few weeks. I'm aware that it's been deprecated in favor of a more general WebHooks mechanism, but the docs are not very clear on exactly how one would instantiate the general mechanism to get back what the existing one does.
What is the easiest way to replicate the functionality that's going away?
github
edited Dec 1 '18 at 14:29
Catalin Hritcu
405411
asked Nov 22 '18 at 0:19
Benjamin PierceBenjamin Pierce
33919
add a comment |
I'm part of several teams that depend heavily on GitHub's convenient "send an email every time anyone pushes commits" service, which is slated to disappear in a few weeks. I'm aware that it's been deprecated in favor of a more general WebHooks mechanism, but the docs are not very clear on exactly how one would instantiate the general mechanism to get back what the existing one does.
What is the easiest way to replicate the functionality that's going away?
github
edited Dec 1 '18 at 14:29
Catalin Hritcu
405411
asked Nov 22 '18 at 0:19
Benjamin PierceBenjamin Pierce
33919
I'm part of several teams that depend heavily on GitHub's convenient "send an email every time anyone pushes commits" service, which is slated to disappear in a few weeks. I'm aware that it's been deprecated in favor of a more general WebHooks mechanism, but the docs are not very clear on exactly how one would instantiate the general mechanism to get back what the existing one does.
What is the easiest way to replicate the functionality that's going away?
github
github
edited Dec 1 '18 at 14:29
Catalin Hritcu
405411
asked Nov 22 '18 at 0:19
Benjamin PierceBenjamin Pierce
33919
edited Dec 1 '18 at 14:29
Catalin Hritcu
405411
asked Nov 22 '18 at 0:19
Benjamin PierceBenjamin Pierce
33919
edited Dec 1 '18 at 14:29
Catalin Hritcu
405411
edited Dec 1 '18 at 14:29
Catalin Hritcu
405411
edited Dec 1 '18 at 14:29
Catalin Hritcu
405411
405411
asked Nov 22 '18 at 0:19
Benjamin PierceBenjamin Pierce
33919
asked Nov 22 '18 at 0:19
Benjamin PierceBenjamin Pierce
33919
asked Nov 22 '18 at 0:19
Benjamin PierceBenjamin Pierce
33919
33919
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Beside the original post (Replacing Services with webhooks), you have:
GitHub Actions, still in beta, but which should make it possible to accomplishes this (registration here).
efforts made to look for a webhook-based alternative.
For instance:pyinstaller/pyinstallerissue 3579. But there are no clear answer yet.
answered Nov 22 '18 at 5:56
VonCVonC
853k30127173281
1
Thank you -- GitHub Actions do indeed seem promising. (I'm still surprised that apparently no one has implemented a turnkey solution already. Are there really so few people wanting an email per push on a repo that they own or contribute heavily to? Seems like a very natural mode of use to me, but perhaps I have a deep misunderstanding of the Right Way to get work done with git...)
– Benjamin Pierce
Nov 22 '18 at 18:34
1
Here is confirmation from GitHub that "it should be possible to build an Action that accomplishes this": twitter.com/mcolyer/status/1068304552372273153
– Catalin Hritcu
Dec 1 '18 at 11:19
1
It would be great if someone with access to the GitHub Actions beta could try this out. Unfortunately, I have no beta access.
– Catalin Hritcu
Dec 1 '18 at 11:19
@CatalinHritcu you can register for their beta here -> github.com/features/actions/signup/?account=
– cecil merrel aka bringrainfire
Dec 4 '18 at 16:42
2
It seems slightly ridiculous that there apparently isn't currently a straightforward way to retain push notification emails. This seems like a very common use case and I would have expected GitHub to provide some kind of transition path by now, especially as they're going to stop working at the end of January 2019.
– Tim Angus
Jan 10 at 10:57
|
show 2 more comments
As far as I can tell, GitHub has now restored the previous functionality and even documented it again: https://help.github.com/articles/about-email-notifications-for-pushes-to-your-repository
answered Feb 5 at 13:44
Catalin HritcuCatalin Hritcu
405411
Interesting. Upvoted. Maybe related to github.blog/changelog/…
– VonC
Feb 5 at 13:59
add a comment |
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%2f53422244%2fhow-to-get-github-commit-notifications-by-email-after-january%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Beside the original post (Replacing Services with webhooks), you have:
GitHub Actions, still in beta, but which should make it possible to accomplishes this (registration here).
efforts made to look for a webhook-based alternative.
For instance:pyinstaller/pyinstallerissue 3579. But there are no clear answer yet.
answered Nov 22 '18 at 5:56
VonCVonC
853k30127173281
1
Thank you -- GitHub Actions do indeed seem promising. (I'm still surprised that apparently no one has implemented a turnkey solution already. Are there really so few people wanting an email per push on a repo that they own or contribute heavily to? Seems like a very natural mode of use to me, but perhaps I have a deep misunderstanding of the Right Way to get work done with git...)
– Benjamin Pierce
Nov 22 '18 at 18:34
1
Here is confirmation from GitHub that "it should be possible to build an Action that accomplishes this": twitter.com/mcolyer/status/1068304552372273153
– Catalin Hritcu
Dec 1 '18 at 11:19
1
It would be great if someone with access to the GitHub Actions beta could try this out. Unfortunately, I have no beta access.
– Catalin Hritcu
Dec 1 '18 at 11:19
@CatalinHritcu you can register for their beta here -> github.com/features/actions/signup/?account=
– cecil merrel aka bringrainfire
Dec 4 '18 at 16:42
2
It seems slightly ridiculous that there apparently isn't currently a straightforward way to retain push notification emails. This seems like a very common use case and I would have expected GitHub to provide some kind of transition path by now, especially as they're going to stop working at the end of January 2019.
– Tim Angus
Jan 10 at 10:57
|
show 2 more comments
Beside the original post (Replacing Services with webhooks), you have:
GitHub Actions, still in beta, but which should make it possible to accomplishes this (registration here).
efforts made to look for a webhook-based alternative.
For instance:pyinstaller/pyinstallerissue 3579. But there are no clear answer yet.
answered Nov 22 '18 at 5:56
VonCVonC
853k30127173281
1
Thank you -- GitHub Actions do indeed seem promising. (I'm still surprised that apparently no one has implemented a turnkey solution already. Are there really so few people wanting an email per push on a repo that they own or contribute heavily to? Seems like a very natural mode of use to me, but perhaps I have a deep misunderstanding of the Right Way to get work done with git...)
– Benjamin Pierce
Nov 22 '18 at 18:34
1
Here is confirmation from GitHub that "it should be possible to build an Action that accomplishes this": twitter.com/mcolyer/status/1068304552372273153
– Catalin Hritcu
Dec 1 '18 at 11:19
1
It would be great if someone with access to the GitHub Actions beta could try this out. Unfortunately, I have no beta access.
– Catalin Hritcu
Dec 1 '18 at 11:19
@CatalinHritcu you can register for their beta here -> github.com/features/actions/signup/?account=
– cecil merrel aka bringrainfire
Dec 4 '18 at 16:42
2
It seems slightly ridiculous that there apparently isn't currently a straightforward way to retain push notification emails. This seems like a very common use case and I would have expected GitHub to provide some kind of transition path by now, especially as they're going to stop working at the end of January 2019.
– Tim Angus
Jan 10 at 10:57
|
show 2 more comments
Beside the original post (Replacing Services with webhooks), you have:
GitHub Actions, still in beta, but which should make it possible to accomplishes this (registration here).
efforts made to look for a webhook-based alternative.
For instance:pyinstaller/pyinstallerissue 3579. But there are no clear answer yet.
answered Nov 22 '18 at 5:56
VonCVonC
853k30127173281
Beside the original post (Replacing Services with webhooks), you have:
GitHub Actions, still in beta, but which should make it possible to accomplishes this (registration here).
efforts made to look for a webhook-based alternative.
For instance:pyinstaller/pyinstallerissue 3579. But there are no clear answer yet.
answered Nov 22 '18 at 5:56
VonCVonC
853k30127173281
edited Dec 4 '18 at 16:56
answered Nov 22 '18 at 5:56
VonCVonC
853k30127173281
answered Nov 22 '18 at 5:56
VonCVonC
853k30127173281
answered Nov 22 '18 at 5:56
VonCVonC
853k30127173281
853k30127173281
1
Thank you -- GitHub Actions do indeed seem promising. (I'm still surprised that apparently no one has implemented a turnkey solution already. Are there really so few people wanting an email per push on a repo that they own or contribute heavily to? Seems like a very natural mode of use to me, but perhaps I have a deep misunderstanding of the Right Way to get work done with git...)
– Benjamin Pierce
Nov 22 '18 at 18:34
1
Here is confirmation from GitHub that "it should be possible to build an Action that accomplishes this": twitter.com/mcolyer/status/1068304552372273153
– Catalin Hritcu
Dec 1 '18 at 11:19
1
It would be great if someone with access to the GitHub Actions beta could try this out. Unfortunately, I have no beta access.
– Catalin Hritcu
Dec 1 '18 at 11:19
@CatalinHritcu you can register for their beta here -> github.com/features/actions/signup/?account=
– cecil merrel aka bringrainfire
Dec 4 '18 at 16:42
2
It seems slightly ridiculous that there apparently isn't currently a straightforward way to retain push notification emails. This seems like a very common use case and I would have expected GitHub to provide some kind of transition path by now, especially as they're going to stop working at the end of January 2019.
– Tim Angus
Jan 10 at 10:57
|
show 2 more comments
1
Thank you -- GitHub Actions do indeed seem promising. (I'm still surprised that apparently no one has implemented a turnkey solution already. Are there really so few people wanting an email per push on a repo that they own or contribute heavily to? Seems like a very natural mode of use to me, but perhaps I have a deep misunderstanding of the Right Way to get work done with git...)
– Benjamin Pierce
Nov 22 '18 at 18:34
1
Here is confirmation from GitHub that "it should be possible to build an Action that accomplishes this": twitter.com/mcolyer/status/1068304552372273153
– Catalin Hritcu
Dec 1 '18 at 11:19
1
It would be great if someone with access to the GitHub Actions beta could try this out. Unfortunately, I have no beta access.
– Catalin Hritcu
Dec 1 '18 at 11:19
@CatalinHritcu you can register for their beta here -> github.com/features/actions/signup/?account=
– cecil merrel aka bringrainfire
Dec 4 '18 at 16:42
2
It seems slightly ridiculous that there apparently isn't currently a straightforward way to retain push notification emails. This seems like a very common use case and I would have expected GitHub to provide some kind of transition path by now, especially as they're going to stop working at the end of January 2019.
– Tim Angus
Jan 10 at 10:57
1
1
Thank you -- GitHub Actions do indeed seem promising. (I'm still surprised that apparently no one has implemented a turnkey solution already. Are there really so few people wanting an email per push on a repo that they own or contribute heavily to? Seems like a very natural mode of use to me, but perhaps I have a deep misunderstanding of the Right Way to get work done with git...)
– Benjamin Pierce
Nov 22 '18 at 18:34
Thank you -- GitHub Actions do indeed seem promising. (I'm still surprised that apparently no one has implemented a turnkey solution already. Are there really so few people wanting an email per push on a repo that they own or contribute heavily to? Seems like a very natural mode of use to me, but perhaps I have a deep misunderstanding of the Right Way to get work done with git...)
– Benjamin Pierce
Nov 22 '18 at 18:34
1
1
Here is confirmation from GitHub that "it should be possible to build an Action that accomplishes this": twitter.com/mcolyer/status/1068304552372273153
– Catalin Hritcu
Dec 1 '18 at 11:19
Here is confirmation from GitHub that "it should be possible to build an Action that accomplishes this": twitter.com/mcolyer/status/1068304552372273153
– Catalin Hritcu
Dec 1 '18 at 11:19
1
1
It would be great if someone with access to the GitHub Actions beta could try this out. Unfortunately, I have no beta access.
– Catalin Hritcu
Dec 1 '18 at 11:19
It would be great if someone with access to the GitHub Actions beta could try this out. Unfortunately, I have no beta access.
– Catalin Hritcu
Dec 1 '18 at 11:19
@CatalinHritcu you can register for their beta here -> github.com/features/actions/signup/?account=
– cecil merrel aka bringrainfire
Dec 4 '18 at 16:42
@CatalinHritcu you can register for their beta here -> github.com/features/actions/signup/?account=
– cecil merrel aka bringrainfire
Dec 4 '18 at 16:42
2
2
It seems slightly ridiculous that there apparently isn't currently a straightforward way to retain push notification emails. This seems like a very common use case and I would have expected GitHub to provide some kind of transition path by now, especially as they're going to stop working at the end of January 2019.
– Tim Angus
Jan 10 at 10:57
It seems slightly ridiculous that there apparently isn't currently a straightforward way to retain push notification emails. This seems like a very common use case and I would have expected GitHub to provide some kind of transition path by now, especially as they're going to stop working at the end of January 2019.
– Tim Angus
Jan 10 at 10:57
|
show 2 more comments
As far as I can tell, GitHub has now restored the previous functionality and even documented it again: https://help.github.com/articles/about-email-notifications-for-pushes-to-your-repository
answered Feb 5 at 13:44
Catalin HritcuCatalin Hritcu
405411
Interesting. Upvoted. Maybe related to github.blog/changelog/…
– VonC
Feb 5 at 13:59
add a comment |
As far as I can tell, GitHub has now restored the previous functionality and even documented it again: https://help.github.com/articles/about-email-notifications-for-pushes-to-your-repository
answered Feb 5 at 13:44
Catalin HritcuCatalin Hritcu
405411
Interesting. Upvoted. Maybe related to github.blog/changelog/…
– VonC
Feb 5 at 13:59
add a comment |
As far as I can tell, GitHub has now restored the previous functionality and even documented it again: https://help.github.com/articles/about-email-notifications-for-pushes-to-your-repository
answered Feb 5 at 13:44
Catalin HritcuCatalin Hritcu
405411
As far as I can tell, GitHub has now restored the previous functionality and even documented it again: https://help.github.com/articles/about-email-notifications-for-pushes-to-your-repository
answered Feb 5 at 13:44
Catalin HritcuCatalin Hritcu
405411
answered Feb 5 at 13:44
Catalin HritcuCatalin Hritcu
405411
answered Feb 5 at 13:44
Catalin HritcuCatalin Hritcu
405411
answered Feb 5 at 13:44
Catalin HritcuCatalin Hritcu
405411
405411
Interesting. Upvoted. Maybe related to github.blog/changelog/…
– VonC
Feb 5 at 13:59
add a comment |
Interesting. Upvoted. Maybe related to github.blog/changelog/…
– VonC
Feb 5 at 13:59
Interesting. Upvoted. Maybe related to github.blog/changelog/…
– VonC
Feb 5 at 13:59
Interesting. Upvoted. Maybe related to github.blog/changelog/…
– VonC
Feb 5 at 13:59
add a comment |
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%2f53422244%2fhow-to-get-github-commit-notifications-by-email-after-january%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
