gitlab-org--gitlab-foss/app/models/protected_branch.rb

class ProtectedBranch < ActiveRecord::Base
  include Gitlab::ShellAdapter
  include ProtectedRef

  has_many :merge_access_levels, dependent: :destroy
  has_many :push_access_levels, dependent: :destroy

  validates :merge_access_levels, length: { is: 1, message: "are restricted to a single instance per protected branch." }
  validates :push_access_levels, length: { is: 1, message: "are restricted to a single instance per protected branch." }

  accepts_nested_attributes_for :push_access_levels
  accepts_nested_attributes_for :merge_access_levels
end
ProtectedBranches model, Master permission for repo\n Allow push to protected branch for masters only 2012-02-15 20:02:33 +00:00			`class ProtectedBranch < ActiveRecord::Base`
replace Gitolited mixin with Gitlab::ShellAdapter 2013-03-21 19:01:14 +00:00			`include Gitlab::ShellAdapter`
Extract ProtectedRef Concern 2017-04-03 14:17:24 +00:00			`include ProtectedRef`
ProtectedBranches model, Master permission for repo\n Allow push to protected branch for masters only 2012-02-15 20:02:33 +00:00
Backport changes from gitlab-org/gitlab-ee!581 to CE. !581 has a lot of changes that would cause merge conflicts if not properly backported to CE. This commit/MR serves as a better foundation for gitlab-org/gitlab-ee!581. = Changes = 1. Move from `has_one {merge,push}_access_level` to `has_many`, with the `length` of the association limited to `1`. This is _effectively_ a `has_one` association, but should cause less conflicts with EE, which is set to `has_many`. This has a number of related changes in the views, specs, and factories. 2. Make `gon` variable loading more consistent (with EE!581) in the `ProtectedBranchesController`. Also use `::` to prefix the `ProtectedBranches` services, because this is required in EE. 3. Extract a `ProtectedBranchAccess` concern from the two access level models. This concern only has a single `humanize` method here, but will have more methods in EE. 4. Add `form_errors` to the protected branches creation form. This is not strictly required for EE compatibility, but was an oversight nonetheless. 2016-08-16 05:09:13 +00:00			`has_many :merge_access_levels, dependent: :destroy`
			`has_many :push_access_levels, dependent: :destroy`
Add models for the protected branch access levels. - And hook up their associations. 2016-07-05 07:40:42 +00:00
Enable Rails/Validation 2017-02-22 00:40:04 +00:00			`validates :merge_access_levels, length: { is: 1, message: "are restricted to a single instance per protected branch." }`
			`validates :push_access_levels, length: { is: 1, message: "are restricted to a single instance per protected branch." }`
Backport changes from gitlab-org/gitlab-ee!581 to CE. !581 has a lot of changes that would cause merge conflicts if not properly backported to CE. This commit/MR serves as a better foundation for gitlab-org/gitlab-ee!581. = Changes = 1. Move from `has_one {merge,push}_access_level` to `has_many`, with the `length` of the association limited to `1`. This is _effectively_ a `has_one` association, but should cause less conflicts with EE, which is set to `has_many`. This has a number of related changes in the views, specs, and factories. 2. Make `gon` variable loading more consistent (with EE!581) in the `ProtectedBranchesController`. Also use `::` to prefix the `ProtectedBranches` services, because this is required in EE. 3. Extract a `ProtectedBranchAccess` concern from the two access level models. This concern only has a single `humanize` method here, but will have more methods in EE. 4. Add `form_errors` to the protected branches creation form. This is not strictly required for EE compatibility, but was an oversight nonetheless. 2016-08-16 05:09:13 +00:00
			`accepts_nested_attributes_for :push_access_levels`
			`accepts_nested_attributes_for :merge_access_levels`
ProtectedBranches model, Master permission for repo\n Allow push to protected branch for masters only 2012-02-15 20:02:33 +00:00			`end`