• Bob Van Landuyt's avatar
    Early migrations populating fork-networks: no-op · 7e00adcc
    Bob Van Landuyt authored
    Since populating the fork networks was scheduled multiple times
    because of bugs that needed to be fixed:
    
    - !15595/
      Creating fork networks for projects that were missing the root of
      the fork network.
    
    - !15709
      The API allowed creating forked_project_links without
      fork_network_members.
    
    Scheduling this migration multiple times would case it to run
    concurrently. Which in turn would try to insert the same data into
    `fork_network_members` causing duplicate key errors.
    
    This avoids running the migration multiple times.
    7e00adcc
Name
Last commit
Last update
..
fixtures Loading commit data...
migrate Loading commit data...
post_migrate Loading commit data...
schema.rb Loading commit data...
seeds.rb Loading commit data...