Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-4028

Initial repository setup for RHDH plugins

Prepare for Y ReleasePrepare for Z ReleaseRemove QuarterXMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Critical Critical
    • 1.4
    • None
    • Build
    • None
    • Initial repository setup for RHDH plugins
    • L
    • False
    • Hide

      None

      Show
      None
    • False
    • RHIDP-3962rhdh-plugins repository and automation
    • To Do
    • RHIDP-3962 - rhdh-plugins repository and automation
    • QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
    • 67% To Do, 33% In Progress, 0% Done

      We need a repeatable process for creating a fork of BCP, then cleaning out the existing workspaces and switching it to a new publishing org/namespace.

      This could involve:

      git clone ... new-folder && cd new-folder
git remote rm origin
git remote add origin path-to-new-repo
git rm -fr workspaces/* && git commit -s -m "remove other workspaces" .
# then edit all the scripts to use new default namespace instead of @backstage-community, perhaps with sed 
# then create a new org on npmjs.com, create a secret for publishing, and upload that into GH for the new repo's config
#

            bgriggs@redhat.com Bethany Griggs
            nickboldt Nick Boldt
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: