> * I don’t think a flood of notifications from the import is a problem.
It’s a one time hassle, and having the actual user links is nice for
GitHub’s cross linking system.
> I agree with Ryan - I'd be willing to bulk-delete 1000 notifications if
it means preserving hyperlinks to people
I'd
It seems not new - I don't figure out why this is not published as a public
API yet but according to the comments there, it could be buggy/unstable
(still worth a try to me).
2022年6月24日(金) 0:26 Tomoko Uchida :
> I just browsed through this article about the "import issues" API (looks
> pretty
I just browsed through this article about the "import issues" API (looks
pretty new and on technical preview status?)
https://gist.github.com/jonmagic/5282384165e0f86ef105
Seems it solves many of our considerations - preserving original timestamp,
bulk importing issue comments, and not triggering
oh phew! glad to hear this was expected
On Thu, Jun 23, 2022 at 10:17 AM Tomoko Uchida
wrote:
>
> > Many comments were lost in the transfer. The last one in the copy is
> > only about 1/4 of the way through this gigantic issue. This really is
> > a blocker I think.
>
> I limited the number of
> Many comments were lost in the transfer. The last one in the copy is
> only about 1/4 of the way through this gigantic issue. This really is
> a blocker I think.
I limited the number of comments per issue up to ten for testing. We can
migrate literally all comments - one by one.
Tomoko
Hi,
I have little now to carefully read/respond to all replies right now, but
just wanted to answer this.
> Will it be possible to preserve links from issues -> pull requests?
Yes it's a bit cumbersome (and it could be difficult to make sure that all
links to PRs are covered - it's not solid
Interesting, thanks Rob. I see the attachments have been ported in that
article as well - something the official API is not able to do.
https://jira.spring.io/browse/DATACMNS-617?redirect=false
https://github.com/spring-projects/spring-data-commons/issues/1080
Dawid
On Thu, Jun 23, 2022 at 3:26
I didn't read the entire thread, so apologies if this is a duplicate:
Did you check
https://spring.io/blog/2021/01/07/spring-data-s-migration-from-jira-to-github-issues
They especially write there is an api that doesn't trigger notifications.
It is documented here:
Yes thank you! You say this is not difficult, but it looks like a big
job to me! Here are a bunch of things I noticed that we would ideally
address (from looking at one long and complex issue, LUCENE-9004). I
wouldn't be so bold as to say these should block us from proceeding if
they're not
