u/ewong/rhodecode-enterprise-ce-fork Files · rhodecode/lib/dbmigrate/migrate.cfg

git: use force fetch and update for target ref. This solves a case...

git: use force fetch and update for target ref. This solves a case when in PRs a target is force updated and is out of sync. Before we used a pull which --ff-only fails obviosly because two are out of sync. This change uses new logic that resets the target branch according to the source target branch allowing smooth merge simulation.

marcink - - Load All Authors

File last commit:

r1:854a839a default


                r2784:e8c62649

default

Download file

             migrate.cfg
        
                    20 lines
            
             | 1017 B
            
                | text/x-ini
            
             |
                IniLexer
            
             / rhodecode / lib / dbmigrate / migrate.cfg
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      [db_settings]

      # Used to identify which repository this database is versioned under.

      # You can use the name of your project.

      repository_id=rhodecode_db_migrations

      # The name of the database table used to track the schema version.

      # This name shouldn't already be used by your project.

      # If this is changed once a database is under version control, you'll need to 

      # change the table name in each database too. 

      version_table=db_migrate_version

      # When committing a change script, Migrate will attempt to generate the 

      # sql for all supported databases; normally, if one of them fails - probably

      # because you don't have that database installed - it is ignored and the 

      # commit continues, perhaps ending successfully. 

      # Databases in this list MUST compile successfully during a commit, or the 

      # entire commit will fail. List the databases your application will actually 

      # be using to ensure your updates to that database work properly.

      # This must be a list; example: ['postgres','sqlite']

      required_dbs=['sqlite']

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

				[db_settings]
				# Used to identify which repository this database is versioned under.
				# You can use the name of your project.
				repository_id=rhodecode_db_migrations

				# The name of the database table used to track the schema version.
				# This name shouldn't already be used by your project.
				# If this is changed once a database is under version control, you'll need to
				# change the table name in each database too.
				version_table=db_migrate_version

				# When committing a change script, Migrate will attempt to generate the
				# sql for all supported databases; normally, if one of them fails - probably
				# because you don't have that database installed - it is ignored and the
				# commit continues, perhaps ending successfully.
				# Databases in this list MUST compile successfully during a commit, or the
				# entire commit will fail. List the databases your application will actually
				# be using to ensure your updates to that database work properly.
				# This must be a list; example: ['postgres','sqlite']
				required_dbs=['sqlite']