- Dec 12, 2017
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- Dec 11, 2017
-
-
TM Lee authored
- Create MemberPresenter alongside with GroupMemberPresenter and ProjectMemberPresenter - Make Member model Presentable - Move action_member_permission from MembersHelper into the MemberPresenter - Added rspec using double, separate specs for GroupMemberPresenter and ProjectMemberPresenter Fixes #28004. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- Dec 05, 2017
-
-
Matija Čupić authored
-
Felipe Artur authored
-
- Oct 30, 2017
-
-
Shinya Maeda authored
-
- Oct 05, 2017
-
-
Shinya Maeda authored
-
Grzegorz Bizon authored
Conflicts: app/presenters/ci/pipeline_presenter.rb
-
- Oct 04, 2017
-
-
Oswaldo Ferreira authored
-
- Sep 04, 2017
-
-
Shinya Maeda authored
-
- Aug 07, 2017
-
-
Jarka Kadlecova authored
-
- Aug 02, 2017
-
-
Robert Speicher authored
-
- Aug 01, 2017
-
-
Robert Speicher authored
-
- Jul 12, 2017
-
-
Clement Ho authored
-
- Jul 11, 2017
-
-
Clement Ho authored
-
Clement Ho authored
-
- Jul 10, 2017
-
-
Clement Ho authored
-
- Jul 07, 2017
-
-
Shinya Maeda authored
-
Shinya Maeda authored
Fix static-snalysis Move the precedence of group secure variable before project secure variable. Allow project_id to be null. Separate Ci::VariableProject and Ci::VariableGroup Add the forgotton files Add migration file to update type of ci_variables Fix form_for fpr VariableProject Fix test Change the table structure according to the yorik advice Add necessary migration files. Remove unnecessary migration spec. Revert safe_model_attributes.yml Fix models Fix spec Avoid self.variable. Use becomes for correct routing. Use unique index on group_id and key Add null: false for t.timestamps Fix schema version Rename VariableProject and VariableGroup to ProjectVariable and GroupVariable Rename the rest of them Add the rest of files Basic BE change Fix static-snalysis Move the precedence of group secure variable before project secure variable. Allow project_id to be null. Separate Ci::VariableProject and Ci::VariableGroup Add the forgotton files Add migration file to update type of ci_variables Fix form_for fpr VariableProject Fix test Change the table structure according to the yorik advice Add necessary migration files. Remove unnecessary migration spec. Revert safe_model_attributes.yml Fix models Fix spec Avoid self.variable. Use becomes for correct routing. Use unique index on group_id and key Add null: false for t.timestamps Fix schema version Rename VariableProject and VariableGroup to ProjectVariable and GroupVariable Rename the rest of them Add the rest of files Implement CURD Rename codes related to VariableGroup and VariableProject FE part Remove unneccesary changes Make Fe code up-to-date Add protected flag to migration file Protected group variables essential package Update schema Improve doc Fix logic and spec for models Fix logic and spec for controllers Fix logic and spec for views(pre feature) Add feature spec Fixed bugs. placeholder. reveal button. doc. Add changelog Remove unnecessary comment godfat nice catches Improve secret_variables_for arctecture Fix spec Fix StaticAnlysys & path_regex spec Revert "Improve secret_variables_for arctecture" This reverts commit c3216ca212322ecf6ca534cb12ce75811a4e77f1. Use ayufan suggestion for secret_variables_for Use find instead of find_by Fix spec message for variable is invalid Fix spec remove variable.group_id = group.id godffat spec nitpicks Use include Gitlab::Routing.url_helpers for presenter spec
-
- Jul 06, 2017
-
-
Yorick Peterse authored
This removes the need for relying on Rails' "dependent" option for data removal, which is _incredibly_ slow (even when using :delete_all) when deleting large amounts of data. This also ensures data consistency is enforced on DB level and not on application level (something Rails is really bad at). This commit also includes various migrations to add foreign keys to tables that eventually point to "projects" to ensure no rows get orphaned upon removing a project.
-
- Jun 21, 2017
-
-
Grzegorz Bizon authored
-
- Jun 09, 2017
-
-
Adam Niedzielski authored
-
- Jun 02, 2017
-
-
Alexander Randa authored
-
- Jun 01, 2017
-
-
- May 12, 2017
-
-
Sean McGivern authored
I don't know why this happens exactly, but given an upstream and fork repository from a customer, both of which required GC, resolving conflicts would corrupt the fork so badly that it couldn't be cloned. This isn't a perfect fix for that case, because the MR may still need to be merged manually, but it does ensure that the repository is at least usable. My best guess is that when we generate the index for the conflict resolution (which we previously did in the target project), we obtain a reference to an OID that doesn't exist in the source, even though we already fetch the refs from the target into the source. Explicitly setting the source project as the place to get the merge index from seems to prevent repository corruption in this way.
-
- May 09, 2017
-
-
Fatih Acet authored
-
- Apr 06, 2017
-
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
Not only tracking auto-cancelling in pipelines, we'll also track this in jobs because pipelines could be retried and the information would get lost when this happened. Also erase auto-cancelling relation for pipelines when they're retried.
-
- Apr 05, 2017
-
-
Lin Jen-Shin authored
-
- Mar 06, 2017
-
-
Jose Ivan Vargas authored
-
Jose Ivan Vargas authored
Also fixed naming of a test in the deploy_keys_presenter
-
Jose Ivan Vargas authored
Added specs for the deploy_keys_presenter and added a new method in the presenter called #key_available? Fixed some minor UX inconsistencies and added a concern to handle redirection
-
Grzegorz Bizon authored
-
- Feb 23, 2017
-
-
Douwe Maan authored
This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
-
Douwe Maan authored
-
- Jan 18, 2017
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-