- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2017 09:21 AM
Hi Sahikanth,
There is currently no way to point to a new repo on the instance. There are two alternatives.
First, you can use the clone repo as you noted. Once cloned, you need to remove the original app and import the app from the new repo.
The second is similar only you export your app to an update set, delete it, create the new repo, import the update set and reconnect to the new repo.
As you can see, both involve deleting the app on the instance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2017 09:25 AM
Thank you, that make sense. I was checking is there anyway other than two above to change pointers. Looks like system has a secret way to keep configuration information other than sys_repo_config table, may be in a metadata.
Anyway, thanks for confirming current possibilities. Appreciate your quick help!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2018 11:53 AM
Cannot deploy to two gits? that is a serious limitation 😞
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2022 10:30 AM
Hi John,
This is old...but how is this limiting you?
If you wanted to keep two repos the same, you could push to one repo (the main one) fork it and have it mirrored to the forked repo. This would achieve the same thing as "deploy[ing] to two gits" unless you mean deploying to both GitLab AND GitHub...then, you'd be right...but I'd have no idea why you'd want to do that anyways.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2022 02:20 PM
Changing the repo your application is associated with is possible now, but not very intuitive; almost actively obfuscated. I just wrote an article on how to do do it, here.
