- 11 Oct, 2016 1 commit
-
-
tiagonbotelho authored
-
- 10 Oct, 2016 1 commit
-
-
Adam Niedzielski authored
Fixes #21800.
-
- 09 Oct, 2016 1 commit
-
-
tiagonbotelho authored
removes inconsistency regarding tagging immediately as merged once you create a branch using new branch button and adds changelog entry
-
- 05 Oct, 2016 1 commit
-
-
Marc Siegfriedt authored
add docs and tests - add additional validation allow move without content updated response
-
- 04 Oct, 2016 1 commit
-
-
Z.J. van de Weg authored
-
- 20 Sep, 2016 1 commit
-
-
Dan Dunckel authored
-
- 19 Sep, 2016 1 commit
-
-
Dan Dunckel authored
-
- 14 Sep, 2016 1 commit
-
-
Valery Sizov authored
-
- 12 Sep, 2016 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 10 Sep, 2016 1 commit
-
-
tiagonbotelho authored
refactors update file
-
- 07 Sep, 2016 2 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
- 02 Sep, 2016 2 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
- 01 Sep, 2016 1 commit
-
-
Stan Hu authored
If `git gc` runs and `Repository` has an instance to `Rugged::Repository`, a bug in libgit2 may cause the instance to return a stale value or a missing branch. This change not only optimizes the branch lookup so we don't have to iterate through every branch, but it also works around the `git gc` issue by forcing a repository reload every time `Repository#find_branch` is called. See: https://github.com/libgit2/libgit2/issues/1534 Closes #15392, #21470
-
- 25 Aug, 2016 1 commit
-
-
Hannes Rosenögger authored
This commit makes sure that the project icon is being read from the default branch instead of 'master'
-
- 19 Aug, 2016 1 commit
-
-
Gokmen Goksel authored
Koding: #index: landing page for Koding integration If enabled it will provide a link to open remote Koding instance url for now we are also providing the sneak preview video for how integration works in detail. Repository: check whether .koding.yml file exists on repository Projects: landing page: show Run in IDE (Koding) button if repo has stack file Projects: MR: show Run in IDE Koding button if repo has stack file on active branch ProjectHelpers: add_koding_stack: stack generator for provided project With this helper we will auto-generate the required stack template for a given project. For the feature we can request this base template from the running Koding instance on integration. Currently this will provide users to create a t2.nano instance on aws and it'll automatically configures the instance for basic requirements. Projects: empty state and landing page provide shortcuts to create stack projects_helper: use branch on checkout and provide an entry point This ${var.koding_queryString_branch} will be replaced with the branch provided in query string which will allow us to use same stack template for different branches of the same repository. ref: https://github.com/koding/koding/pull/8597/commits/b8c0e43c4c24bf132670aa8a3cfb0d634acfd09b projects_helper: provide sha info in query string to use existing vms With this change we'll be able to query existing vms on Koding side based on the commit id that they've created. ref: https://github.com/koding/koding/pull/8597/commits/1d630fadf31963fa6ccd3bed92e526761a30a343 Integration: Docs: Koding documentation added Disable /koding route if integration is disabled Use application settings to enable Koding Projects_helper: better indentation with strip_heredoc usage Projects_helper: return koding_url as is if there is no project provided current_settings: set koding_enabled: false by default Koding_Controller: to render not_found once integration is disabled Dashboard_specs: update spec for Koding enabled case Projects_Helper: make repo dynamic ref: https://github.com/koding/koding/pull/8597/commits/4d615242f45aaea4c4986be84ecc612b0bb1514c Updated documentation to have right format
-
- 17 Aug, 2016 1 commit
-
-
Yorick Peterse authored
GitLab Performance Monitoring is now able to track custom events not directly related to application performance. These events include the number of tags pushed, repositories created, builds registered, etc. The use of these events is to get a better overview of how a GitLab instance is used and how that may affect performance. For example, a large number of Git pushes may have a negative impact on the underlying storage engine. Events are stored in the "events" measurement and are not prefixed with "rails_" or "sidekiq_", this makes it easier to query events with the same name triggered from different parts of the application. All events being stored in the same measurement also makes it easier to downsample data. Currently the following events are tracked: * Creating repositories * Removing repositories * Changing the default branch of a repository * Pushing a new tag * Removing an existing tag * Pushing a commit (along with the branch being pushed to) * Pushing a new branch * Removing an existing branch * Importing a repository (along with the URL we're importing) * Forking a repository (along with the source/target path) * CI builds registered (and when no build could be found) * CI builds being updated * Rails and Sidekiq exceptions Fixes gitlab-org/gitlab-ce#13720
-
- 12 Aug, 2016 1 commit
-
-
Sean McGivern authored
-
- 08 Aug, 2016 1 commit
-
-
Alejandro Rodríguez authored
-
- 06 Aug, 2016 1 commit
-
-
Gabriel Mazetto authored
-
- 03 Aug, 2016 2 commits
-
-
Stan Hu authored
-
Paco Guzman authored
So we have raw_diffs too
-
- 28 Jul, 2016 2 commits
-
-
Alejandro Rodríguez authored
-
Herminio Torres authored
Before when you choose the way of `sort` instead it display the title correctly it was just apply the humanize helper in sort value. E.g. When you choose `Last updated` it should display the title `Last updated` instead of `Recently updated`. This fix makes this correctly displays the title. Change the implementation of the `link_to` `filter_branches_path` - Change the value of the `params[:sort]` in `link_to`. E.g. instead of using `'recently_updated'` is now using `sort_value_recently_updated`. - Change the values of the case in the `branches_sorted_by` method for the values it receives in the `params[:sort]` that are: `nil`, `'name'`, `'updated_desc'`, `'updated_asc'`.
-
- 27 Jul, 2016 1 commit
-
-
tiagonbotelho authored
Project and branch cache is expired when project is still empty or new branch is created. develops tests accordingly Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 26 Jul, 2016 1 commit
-
-
Paco Guzman authored
-
- 25 Jul, 2016 1 commit
-
-
Stan Hu authored
We have a number of bugs caused by cache keys not being flushed properly during deletion of a project. Add the project ID to ensure this never happens. Closes #20027
-
- 24 Jul, 2016 1 commit
-
-
Alejandro Rodríguez authored
This reverts merge request !5375
-
- 22 Jul, 2016 1 commit
-
-
Stan Hu authored
We were seeing a number of error messages when attempting to create a keep-around ref: 1. Failed to create locked file `refs/keep-around/XYZ`: File exists 2. Failed to write reference `refs/keep-around/XYZ`: a reference with that name already exists. I'm not sure how these happen, but I suspect when multiple workers attempt to write the same file we may have an issue. The force parameter should help ensure the file gets created, as well as the rescues to prevent 500 Errors. Rugged/libgit2 unfortunately do not allow you to delete or re-create a reference that has been corrupted, even with the force parameter. Closes #20109
-
- 21 Jul, 2016 2 commits
-
-
Alejandro Rodríguez authored
-
Douglas Barbosa Alexandre authored
Replace invocation of `find` with Ruby code that matches old cached files in a better, and safe way to avoid data-integrity issues.
-
- 20 Jul, 2016 1 commit
-
-
Paco Guzman authored
-
- 19 Jul, 2016 5 commits
-
-
tiagonbotelho authored
same time and writes tests accordingly changes schema.db removes duplicate field inside CHANGELOG fix db/schema
-
tiagonbotelho authored
refactors find_similar_branches method to a one liner
-
tiagonbotelho authored
-
tiagonbotelho authored
-
Valery Sizov authored
-
- 18 Jul, 2016 1 commit
-
-
Rémy Coutable authored
This reverts commit 530f5158. See !4892. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 13 Jul, 2016 1 commit
-
-
Robert Speicher authored
This reverts commit 9ca633eb, reversing changes made to fb229bbf.
-