assignUser commented on issue #3: URL: https://github.com/apache/arrow-java/issues/3#issuecomment-2504515748
@raulcd yes here it is: ```bash # get the open issues with the label -L has to be set to > then open issues (or what ever batch you want to work on seems like the backend can be a bit tricky when transfering a large number of issues gh issue list --label "Component: Java" --state "open" -L 400 --json 'number,labels' > issues.json jq -r '[.[].number] - ['<numbers of issues you want to exclude>'] | map(select(. < '<only transfer issues with issue num smaller than ths'>')) | .[]' issues.json | xargs -I% gh issue transfer % https://github.com/apache/arrow-java ``` > '<only transfer issues with # smaller than ths'>' For both go and java we already had some issue in apache/arrow dealing with the remnants there, these should ofc stay there, as issue numbers are sequential we can just exclude via lt. As mentioned above it's important that the labels you want to carry over already exists in the new repo, otherwise the info will be lost. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
