delta/gitlab/gitlab-ce.git/spec/models, branch remove_sqlite_check

Merge branch 'smarter-diverging-commit-cache-flushing' into 'master'

2016-02-09T17:19:12+00:00


Smarter flushing of branch statistics caches

This basically ensures we only flush caches of branches whenever we really have to. See commit c514f8b850219cd3e5526e73e1d00e6729e2b466 for the details.

cc @joshfng @rspeicher 

See merge request !2769

Smarter flushing of branch statistics caches

2016-02-09T16:17:56+00:00

Instead of flushing the behind/ahead counts for all branches upon every
push we now only flush the cache of branches that actually need to have
these statistics recalculated. There are now basically 2 scenarios and
their effects:

1. A user pushes a commit to the default branch, this results in the
   cache being flushed for all branches.
2. A user pushes to a non default branch, this results in _only_ the
   cache for that branch being flushed.

The existing code (Repository#expire_cache) remains backwards compatible
with the previous behaviour, the new behaviour is only applied when a
branch name is passed as an argument. This ensures that when for example
a project is deleted the cache for all branches is flushed.

Merge branch 'fix/max-attachment-size-setting-validation'

2016-02-09T15:52:20+00:00

Merge branch 'zj/gitlab-ce-unique-milestone-title-per-project'

2016-02-09T12:15:37+00:00

Validate maximum attachment size in application settings

2016-02-09T11:11:16+00:00

`max_attachment_size` in `ApplicationSetting` should be present,
only integers greater than zero are valid.

Closes #13188

Cache various Repository Git operations

2016-02-08T14:40:19+00:00

This caches the output of the following methods:

* Repository#empty?
* Repository#has_visible_content?
* Repository#root_ref

The cache for Repository#has_visible_content? is flushed whenever a
commit is pushed to a new branch or an existing branch is removed.
The cache for Repository#root_ref is only flushed whenever a user
changes the default branch of a project. The cache for Repository#empty?
is never explicitly flushed as there's no need for it.

Validate uniqueness of milestone title per project

2016-02-08T11:45:32+00:00

Fixes #3903

Merge branch 'disable-remove-source-branch' into 'master'

2016-02-04T11:56:58+00:00


Hide remove source branch button when new commit is added to branch

Fixes #3339

This MR hides the 'Remove source branch' button when a new commit is added to the source branch

/cc @DouweM

See merge request !2701

Hide remove source branch button when new commit is added to branch

2016-02-04T10:56:23+00:00

Fixes #3339

This MR hides the 'Remove source branch' button when a new commit is added to the source branch

Merge branch 'wipMergeSpacing' into 'master'

2016-02-04T09:49:54+00:00


No space required after WIP identifier

Fixes #2426 

Currently, the WIP: (or any other variation) prefix of a merge request title must include a trailing space for it to be recognized as a work in progress and prevent merging. 
To resolve this, I added an or pattern to the regexp to look for any one of the three possible delimiters ':', ']', or ' '. This way the trailing space isn't required but it still won't mark any titles beginning with wip as work in progress (e.g. "Wipwap").

See merge request !1876