4 ms·

The problem is github makes all notifications STD-level contagious. They broke out "watching" and "staring" a while ago, but they are still very overzealous wi

by seiji 13y ago

The problem is github makes all notifications STD-level contagious. They broke out "watching" and "staring" a while ago, but they are still very overzealous with notifying everybody about everything. The poster didn't use "send email" API, he was just automatically importing things, and every import triggered emails nonsensically.

giovannibajo1 13y ago
The problem is that GitHub doesn't really have an import/export API; when you migrate from google code or sourceforge, all issues will appear created and commented from your own account, and at the current date/time. I guess there's a commercial reason for this: http://giovanni.bajo.it/post/60836467126/github-is-missing-import-export-for-commercial-reasons http://giovanni.bajo.it/post/60836467126/github-is-missing-i... I was going to make the same mistake myself (thanks OP!). Is there a workaround?
- plorkyeran 13y ago
  > Is there a workaround? Not that I know of. I added a note to the README about it sending lots of emails to help others avoid accidentally doing this, though.
  - badlogic 13y ago
    I was about to send a PR for the README, will save a few folks some headaches.
- aaronbrethorst 13y ago
  > I guess there's a commercial reason for this I doubt that's the case. I bet you that if GitHub were to break out their revenue by plan that the vast majority comes from business plans and GitHub Enterprise. I would be astonished if any of these customers would ever export their dormant repositories for storage. I'm sure that it's just a matter of them prioritizing this vs. the million other things that are on their backlog. As with most other software companies, your best bet would probably be to start emailing their support with requests for it so that they know it's important to the community at large.

4 ms·

The problem is github makes all notifications STD-level contagious. They broke out "watching" and "staring" a while ago, but they are still very overzealous wi

by seiji 13y ago

giovannibajo1 13y ago
The problem is that GitHub doesn't really have an import/export API; when you migrate from google code or sourceforge, all issues will appear created and commented from your own account, and at the current date/time. I guess there's a commercial reason for this: http://giovanni.bajo.it/post/60836467126/github-is-missing-import-export-for-commercial-reasons http://giovanni.bajo.it/post/60836467126/github-is-missing-i... I was going to make the same mistake myself (thanks OP!). Is there a workaround?
- plorkyeran 13y ago
  > Is there a workaround? Not that I know of. I added a note to the README about it sending lots of emails to help others avoid accidentally doing this, though.
  - badlogic 13y ago
    I was about to send a PR for the README, will save a few folks some headaches.
- aaronbrethorst 13y ago
  > I guess there's a commercial reason for this I doubt that's the case. I bet you that if GitHub were to break out their revenue by plan that the vast majority comes from business plans and GitHub Enterprise. I would be astonished if any of these customers would ever export their dormant repositories for storage. I'm sure that it's just a matter of them prioritizing this vs. the million other things that are on their backlog. As with most other software companies, your best bet would probably be to start emailing their support with requests for it so that they know it's important to the community at large.