delta/gitlab/gitlab-ce.git/spec/workers, branch feature/github-edit-path gitlab.com: gitlab-org/gitlab-ce.git Added cron to prune events older than 12 months. 2016-09-07T17:41:25+00:00 Olaf Tomalka olaf.tomalka@gmail.com 2016-09-05T08:18:08+00:00 e25b48ffcf1f7ef31df8d6c3366674e7f5c29893 Since contribution calendar shows only 12 months of activity, events older than that time are not visible anywhere and can be safely pruned saving big amount of database storage. Fixes #21164 
Since contribution calendar shows only 12 months of activity,
events older than that time are not visible anywhere and can be
safely pruned saving big amount of database storage.

Fixes #21164
Project tools visibility level 2016-09-01T14:47:59+00:00 Felipe Artur felipefac@gmail.com 2016-08-01T22:31:21+00:00 892dea67717c0efbd6a28f7639f34535ec0a8747 






Merge branch '21010-emailsonpushworker-incorrectly-claims-deleted-a-commit-after-a-push' into 'master'

2016-08-19T18:16:55+00:00

Douwe Maan
douwe@gitlab.com

2016-08-19T18:16:55+00:00

82a39e3e698b6332c44f036b735ae98926767057


Resolve "EmailsOnPushWorker incorrectly claims deleted a commit after a push"

## What does this MR do?

Fix the comparison order in the emails on push worker, so regular pushes don't show a message about force pushing.

## Are there points in the code the reviewer needs to double check?

Don't think so, it was just a typo: `after_sha` should map to the `source_branch` argument, because it's the head of the comparison.

## Why was this MR needed?

To fix a regression!

## What are the relevant issue numbers?

Closes #21010.

## Does this MR meet the acceptance criteria?

- [x] ~~[CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added~~
- [x] ~~[Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)~~
- [x] ~~API support added~~
- Tests
  - [x] Added for this feature/bug
  - [ ] All builds are passing
- [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [x] Branch has no merge conflicts with `master` (if you do - rebase it please)
- [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)

See merge request !5894





Resolve "EmailsOnPushWorker incorrectly claims deleted a commit after a push"

## What does this MR do?

Fix the comparison order in the emails on push worker, so regular pushes don't show a message about force pushing.

## Are there points in the code the reviewer needs to double check?

Don't think so, it was just a typo: `after_sha` should map to the `source_branch` argument, because it's the head of the comparison.

## Why was this MR needed?

To fix a regression!

## What are the relevant issue numbers?

Closes #21010.

## Does this MR meet the acceptance criteria?

- [x] ~~[CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added~~
- [x] ~~[Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)~~
- [x] ~~API support added~~
- Tests
  - [x] Added for this feature/bug
  - [ ] All builds are passing
- [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [x] Branch has no merge conflicts with `master` (if you do - rebase it please)
- [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)

See merge request !5894






Don't log to STDOUT in specs
2016-08-19T12:08:21+00:00

Sean McGivern
sean@gitlab.com

2016-08-19T12:08:21+00:00

d0fcd13ea34ab1557d8b071c7a1fb117046261cb












Fix force-push message in push emails
2016-08-19T12:07:39+00:00

Sean McGivern
sean@gitlab.com

2016-08-19T12:07:39+00:00

e37c39a21dac3d67c9c589894cf02f3614a04cbe

`after_sha` maps to the source branch, as it's the head of our compare,
so these were just the wrong way around.





`after_sha` maps to the source branch, as it's the head of our compare,
so these were just the wrong way around.







Allow project group links to be expired
2016-08-18T21:45:41+00:00

Sean McGivern
sean@gitlab.com

2016-08-18T21:45:41+00:00

883b96ab6a77175d9bac7f03c325428327359cdd












Ensure last group owner isn't removed on expiry
2016-08-18T20:32:42+00:00

Sean McGivern
sean@gitlab.com

2016-08-18T20:32:42+00:00

d2cd9d96965722cca06792c63d76d2704366d7a5












Merge branch 'master' into expiration-date-on-memberships
2016-08-18T14:54:07+00:00

Sean McGivern
sean@gitlab.com

2016-08-18T14:49:32+00:00

8b1656282bcc39a0c1c7a3dccf74c98b1c3adae2












Merge remote-tracking branch 'origin/master' into pipeline-hooks-without-slack
2016-08-13T09:03:48+00:00

Kamil Trzcinski
ayufan@ayufan.eu

2016-08-13T09:03:48+00:00

4d4ef89cdcb9beca66a13ab2b64e9eb45f8d8256












Simplify the name for data builder, feedback:
2016-08-12T08:09:29+00:00

Lin Jen-Shin
godfat@godfat.org

2016-08-12T08:09:29+00:00

d5264e8804bca70e613c418a9d346f5787c6fc7a

https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5620#note_13671791





https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5620#note_13671791