most repo-settings have been re-created as part of the move.

re-create any settings that are still missing, and add checkmarks to update the list below.

repo settings (as structured in GH web UI):

• general

access

• collaborators & teams ^[1]
• teams & member roles

code & automation

• branches
• tags
• rules
  • rulesets
  • insights
  • bypass requests
• actions
  • general
  • runners
• models
• webhooks ^[2]
• environments ^[3]
• codespaces
• pages
• custom properties

security

• advanced security
• deploy keys
• secrets & variables
  • actions
    • repository secrets (the only populated section under 'actions') ^[4]
      • CYPRESS_TEST_WITHQUOTA_PASSWORD
      • CYPRESS_TEST_WITHQUOTA_USER
      • CHECK_API_TOKEN
      • PR_REVIEW_TOKEN
      • GITLAB_REPOSITORY
      • GITLAB_REPOSITORY_TOKEN
      • JIRA_API_TOKEN
      • JIRA_BASE_URL
      • JIRA_RELEASE_TOKEN
      • JIRA_USER_EMAIL
      • SLACK_RELEASE_WEBHOOK
  • codespaces
  • dependabot

integrations

• github apps ^[5]
  • konflux staging
  • packit-as-a-service
  • red hat konflux
  • slack
  • travis CI
  • jira
  • renovate
• email notifications
• autolink references

notes

1. we may want to leave adding members to last; it might send out email invites
2. the 2 existing webhooks point at RH jira, and seem to be used/triggered by renovate-bot. leaving them out for now, as they need secrets, which i don't have the knowledge of. will revisit webhooks after renovate-bot is added as a member - and those webhooks might get created automatically.
   another thing to consider: the secrets JIRA_API_TOKEN, JIRA_BASE_URL, JIRA_RELEASE_TOKEN, JIRA_USER_EMAIL might be used in these hooks somehow.. in such case tho, i'm not sure why they'd be kept in repo-secrets.
3. the single 'github-pages' env' was not migrated, as it's obsolete (points to the non-existing 'gh-pages' branch)
4. to re-create any necessary secrets, the relevant stakeholders should be reached out. secrets are notated by priority:
   • those in bold text are the only ones crucial for operation, and need to be re-created right away
   • secrets styled as italics text are not critical and can be re-created later
   • the ones marked with a strikethrough are not in use, and can just be omitted for good
5. only jira & renovate were installed manually in the old repo, the other apps are there by default when you create a new repo under RH-insights org'. only org’ admins can install new apps - we might need to reach out to Greg McCullough for permissions, and to Kike for knowledge on renovate setup