- 🆕 Create Repo (IssueOps)
- 🪓 Delete Repo (IssueOps)
- 🏷️ Labelops
- ✨ Reusable Worfklow repo onboarder (IssueOps) (separate repository)
- issue template and issue parsing
- uses GitHub App for authentication
- posting back comment to repo with instructions after initial issue creation
- renames the issue after creation for consistency
- creating repo using Octokit JavaScript SDK
- adds issue label when the repo after job completion
- The solution uses a GitHub App for authentication
- Actions secrets/variables:
- Secret:
PRIVATE_KEY
- Variable:
APP_ID
- Secret:
- Permissions required:
- Repository:
administration
: read/write (for creating/deleting repos)contents
: read/write (for pushing code to the new repo)issues
: read/write (for updating/closing issues)workflows
: read/write (for pushing workflow files)
- Organization:
- none
- Repository:
- Actions secrets/variables:
Create the appropriate labels
gh label create create-repo
gh label create created
gh label create delete-repos
gh label create deleted
Tip
If your terminal isn't running under the cloned repository, you can pass in the --repo
flag to the gh
command. For example:
gh label create create-repo --repo joshjohanning-org/issueops-samples
- This often assumes the org that the IssueOps repo is hosted in is the org you are using for API calls (ie: to create/delete repos). Update the owner as appropriate or modify the issue template to allow that as an input.