📅 5/20 @ 1pm PT - copy GitHub repositories with issues, labels, milestones, and assignees

gr2m commented 3 years ago

💁🏻 copy GitHub repositories with issues, labels, milestones, and assignees 📅 Wednesday, May 20, 2021 🕐 1pm Pacific Time (in your timezone) 🎙️ maybe @xavt? 🏷️ Testing

copy GitHub repositories with issues, labels, milestones, and assignees

This show is a follow up the idea described at https://github.com/gr2m/helpdesk/issues/12. The goal is to create a script to reliably transfer issues from one repository to another. However, before we can write such a script we need a test setup which permits us to quickly create repositories with issues to transfer for testing. The test setup is the scope for this show

Outline

[x] Template repositories and how to create a new repository based on a template using the REST API
[x] Retrieve all issues, labels, milestones, collaborators, and assignees from a repository using GraphQL
[x] Create the issues and comments with the same meta information as in the source repository

Recording

Shownotes

Template repositories
GraphiQL - The GraphQL UI Electron App
Create user-to-server tokens as a better alternative to personal access tokens: https://create-user-to-server-token.netlify.app/ (source code: https://github.com/gr2m/create-user-to-server-token)
The result of this show: the copy-repository CLI

Preparation

[x] Create a test organization with template repositories and collaborators: @Another-Practice-Organization (thanks @xavt)
[x] Prepare a GraphQL query to fetch issues, labels, milestones, collaborators, and assignees
[x] Create a web app to create user-to-server tokens in order to safely share tokens between users that are limited by a GitHub app's permissions and installs.

gr2m commented 3 years ago

One interesting challenge is to remain authorship of the issues when copying. Our script would require an OAuth token for each user that created an issue or a comment.

Sharing personal access tokens for real user accounts is not a good idea, and tokens received from OAuth Apps cannot be restricted to a single organization either. The best approach would be to register a GitHub App, install it on the @Another-Practice-Organization organization, and then use the OAuth flow for the app to create user-to-server tokens, because these tokens in fact are restricted to the app's installations.

gr2m commented 3 years ago

🔴 going live now at https://www.twitch.tv/gregorcodes

gr2m commented 3 years ago

The episode is now on Twitch: https://www.twitch.tv/videos/1029411115

johnjsatter commented 3 years ago

Hey guys. Ty so much. Can I add assign you?

gr2m commented 3 years ago

Glad you like it :)

I'm sorry but I don't understand what you mean with "Can I add assign you?"? Can you explain please?

johnjsatter commented 3 years ago

I just meant add/ assign you as a contact to my private repository

johnjsatter commented 3 years ago

Thank you so much for the comment. Everyone’s helping and I see that. Ty

gr2m commented 3 years ago

I just meant add/ assign you as a contact to my private repository

I cannot provide 1:1 support for free I’m afraid. But if you have any questions about the current topic you can always ask here

gr2m commented 3 years ago

The recording of the video is now on YouTube: https://www.youtube.com/watch?v=zrVfQbiWLbE

gr2m / helpdesk