-
Epic
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
Initial repository setup for RHDH plugins
-
L
-
False
-
-
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
-
22% To Do, 11% In Progress, 67% 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 #
- is related to
-
RHIDP-3962 rhdh-plugins repository and automation
- In Progress