gitlab-org--gitlab-foss/db/migrate/20150219004514_add_events_to_services.rb

# rubocop:disable all
class AddEventsToServices < ActiveRecord::Migration[4.2]
  def change
    add_column :services, :push_events, :boolean, :default => true
    add_column :services, :issues_events, :boolean, :default => true
    add_column :services, :merge_requests_events, :boolean, :default => true
    add_column :services, :tag_push_events, :boolean, :default => true
  end
end
Enable RuboCop for migrations Migrations shouldn't fail RuboCop checks - especially lint checks, such as the nested method check. To avoid changing code in existing migrations, add the magic comment to the top of each of them to skip that file. 2016-06-09 08:39:16 -04:00			`# rubocop:disable all`
Add version 4.2 to all existing migrations DB schema generated by a migration may look different in rails 4 and 5 (because rails 5 may use different default values). For this reason it's important to explicitly set for which rails version a migration was written for. See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912 2018-11-13 02:27:31 -05:00			`class AddEventsToServices < ActiveRecord::Migration[4.2]`
Issue #595: Support Slack notifications upon issue and merge request events 1) Adds a DB migration for all services to toggle on push, issue, and merge events. 2) Upon an issue or merge request event, fire service hooks. 3) Slack service supports custom messages for each of these events. Other services not supported at the moment. 4) Label merge request hooks with their corresponding actions. 2015-02-19 00:02:57 -05:00			`def change`
			`add_column :services, :push_events, :boolean, :default => true`
			`add_column :services, :issues_events, :boolean, :default => true`
			`add_column :services, :merge_requests_events, :boolean, :default => true`
			`add_column :services, :tag_push_events, :boolean, :default => true`
			`end`
			`end`