##// END OF EJS Templates
integrations: refactor/cleanup + features, fixes #4181...
integrations: refactor/cleanup + features, fixes #4181 * added scopes on integrations, scopes are: - repo only - repogroup children only - root repos only - global (any repo) * integrations schemas now have separate section for the settings (eg. slack) and options (eg. scope/enabled) * added descriptions to integration types * added icons to integration types * added 'create new' integration page * added scope of integration to integrations list * added breadcrumbs for each repo/repogroup/global integrations pages * added sorting to integrations list * added pagination to integrations list * added icons to integrations list * added type filter to integrations list * added message to integrations list if none we found * added extra permissions check on integrations views * db migration from 56 => 57 - adds child_repos_only field * added tests for integrations triggered on events * added tests for integrations schemas * added tests for integrations views for repo/repogroup/admin

File last commit:

r1:854a839a default
r731:7a6d3636 default
Show More
migrate-repos.rst
23 lines | 740 B | text/x-rst | RstLexer

Migrating |repos|

If you have installed |RCM| and have |repos| that you wish to migrate into the system, use the following instructions.

  1. On the |RCM| interface, check your |repo| storage location under :menuselection:`Admin --> Settings --> System Info`. For example, Storage location: /home/{username}/repos.
  2. Copy the |repos| that you want |RCM| to manage to this location.
  3. Remap and rescan the |repos|, see :ref:`remap-rescan`

Important

Directories create |repo| groups inside |RCM|.

Importing adds |RCM| git hooks to your |repos|.

You should verify if custom .hg or .hgrc files inside repositories should be adjusted since |RCM| reads the content of them.