Commits on Source (63)
-
Kamil Trzciński authored
-
Kamil Trzciński authored
-
Kamil Trzciński authored
-
Kamil Trzciński authored
-
Stan Hu authored
-
-
Felipe authored
Code improvements, bug fixes, finish documentation and specs
-
Stan Hu authored
-
Felipe authored
-
Kamil Trzciński authored
-
Dmytro Zaporozhets (DZ) authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Steve Halasz authored
If notification_email is blank, it's set from email. If an admin attempted to create a user with an invalid email, an error would be displayed for both fields. Only validate the notification_email if it's different from email.
-
Steve Halasz authored
-
Steve Halasz authored
Getting latest CHANGELOG so I can resolve merge conflict
-
Steve Halasz authored
Get fix for teaspoon tests
-
Winnie authored
-
Alejandro Rodríguez authored
-
Sean McGivern authored
`ProjectTeam#find_member` doesn't take group links into account. It was used in two places: 1. An admin view - it can stay here. 2. `ProjectTeam#member?`, which is often used to decide if a user has access to view something. This second part broke confidential issues viewing. `IssuesFinder` ends up delegating to `Project#authorized_for_user?`, which does consider group links, so users with access to the project via a group link could see confidential issues on the index page. However, `IssuesPolicy` used `ProjectTeam#member?`, so the same user couldn't view the issue when going to it directly.
-
Ahmad Sherif authored
-
Ahmad Sherif authored
-
Ahmad Sherif authored
-
Ahmad Sherif authored
-
Ahmad Sherif authored
-
blackst0ne authored
-
Adam Niedzielski authored
Do not pass project.owner because it may return a group and Labels::FindOrCreateService throws an error in this case. Fixes #23694.
-
blackst0ne authored
-
blackst0ne authored
Merge branch 'bugfix/dragging_milestones' of gitlab.com:blackst0ne/gitlab-ce into bugfix/dragging_milestones
-
Sean McGivern authored
Jira refactoring to jira gem part of gitlab-org/gitlab-ee#1008 Original MR: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2572/commits See merge request !6598
-
Sean McGivern authored
API: Fix booleans not recognized as such when using the `to_boolean` helper Fixes #22831 Fixes #23890 See merge request !7149
-
Rémy Coutable authored
Fix and improve `Sortable.highest_label_priority` Closes #23928 See merge request !7165
-
Rémy Coutable authored
Document admin access requirement for /deploy_keys endpoint Closes #23807 See merge request !7164
-
Winnie authored
-
Winnie authored
-
Sean McGivern authored
Stop unauthorized users dragging on milestone page Closes #13670 See merge request !7113
-
Rémy Coutable authored
Only show one error message for an invalid email Changes it to only validate the notification_email format if it's different from email. Closes #5905 See merge request !7158
-
Sean McGivern authored
Modify GitHub importer to be retryable Closes #23533 See merge request !7003
-
Sean McGivern authored
These changes are targeted for 8.13.2, not 8.14.
-
Phil Hughes authored
-
Phil Hughes authored
-
Dmytro Zaporozhets (DZ) authored
Signed-off-by:
Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Rémy Coutable authored
Replace static fixture by generated one in issue_spec.js ## What does this MR do? - clean up `issue_spec.js` - introduce an alternative approach to #19445 - rename `rake teaspoon` to `rake teaspoon:tests` - introduce `rake teaspoon:fixtures` which generates fixtures using RSpec - introduce `rake teaspoon` which runs `rake teaspoon:fixtures` and `rake teaspoon:tests` ## Why was this MR needed? - many duplications - missing existence checks - missing conditions - static fixtures don't match real views ## Reasoning I want to explain some of my decisions here, so that they stay visible for future discussions. ### Why not HAML? - same number of HAML templates as number of fixtures (many input files) - embedded logic less readable - can not be rendered by JavaScript (because of inline Ruby) ### Why RSpec? - real controllers for fixtures - spys available for mocking - easily report failed fixture generations ### Why not magic_lamp? (#19445) - introduces another dependency/tool - needs to run a server concurrently to teaspoon - makes it harder to use a JavaScript test runner - static HTML files serve faster See merge request !6059
-
Rémy Coutable authored
This param allows to bypass permission check. It is useful for LDAP-sync where even owners don't have the :admin_group_member permission. See https://gitlab.com/gitlab-org/gitlab-ee/blob/6081c37123abae4570f78831b33c2f45f92c2765/app/policies/group_policy.rb#L38 and https://gitlab.com/gitlab-org/gitlab-ee/issues/1159 Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Sean McGivern authored
-
Robert Speicher authored
Delete issue board welcome cookie ## What does this MR do? This was seen in the idea to production demo, because the project had already existed on the exact same URL the cookie already existed which meant the blank state wasn't shown. This MR deletes the cookie on project create. See merge request !6899
-
Stan Hu authored
Use optimistic locking ## What does this MR do? Removes the usage of pessimistic locking in favor of optimistic which is way cheaper and doesn't block database operation. Since this is very simple change it should be safe. If we receive `StaleObjectError` message we will reload object a retry operations in lock. However, I still believe that we need this one: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7005 as this will reduce a load on Database and FS. This changes a behavior from: ### Pesimistic locking (previous behavior) #### For updating 1. SELECT * FOR UPDATE (other updates wait on this) 2. we update ci_pipeline 3. latest_build_status 4. enqueue: (use: transition :created -> :pending) 5. [state_machine] we are in state created, we can go to pending 6. [state_machine] ci_pipeline.status = created 7. [state_machine] ci_pipeline.save 8. [state_machine] after_transition: (if for success): PipelineSuccessWorker on Sidekiq 9. release DB lock #### If no update is required 1. SELECT * FOR UPDATE (other updates wait on this) 2. we update ci_pipeline 3. latest_build_status 4. we are in pending, we can't transition to pending, because it's forbidden 5. release DB lock ### Optimistic locking (implemented by this MR) #### For updating 1. latest_build_status 2. enqueue: (use `transition :created -> :pending`) 3. [state_machine] we are in state created, we can go to pending 4. [state_machine] ci_pipeline.status = created 5. [state_machine] ci_pipeline.save 6. [state_machine] [save] where(lock_version: ci_pipeline.lock_version).update_all(status: :created, updated_at: Time.now) 7. [state_machine] [save] unless we_updated_row then raise ObjectInconsistentError #### If no update is required 1. we update ci_pipeline 2. latest_build_status 3. we are in pending, we can't transition to pending, because it's forbidden ## Why was this MR needed? We have been seeing a number of problems when we migrated Pipeline/Build processing to Sidekiq. Especially we started seeing a lot of blocking queries. We used a pessimistic locking which doesn't seem to be required. This effectively allows us to fix our issues with blocked queries by using more efficient method of operation. ## What are the relevant issue numbers? Issues: https://gitlab.com/gitlab-com/infrastructure/issues/623 and https://gitlab.com/gitlab-com/infrastructure/issues/584, but also there's a bunch of Merge Requests that try to improve behavior of scheduled jobs. cc @pcarranza @yorickpeterse @stanhu See merge request !7040
-
Phil Hughes authored
This prevents VueJS being included in application.js & therefore included on everypage
-
Phil Hughes authored
-
Douwe Maan authored
Pass user instance to Labels::FindOrCreateService or skip_authorization: true ## What does this MR do? It fixes a bug described in #23694 when `project.owner` was passed to `Labels::FindOrCreateService`. `Labels::FindOrCreateService` expected a user instance and `project.owner` may return a group as well. This MR makes sure that we either pass a user instance or `skip_authorization: true`. ## Are there points in the code the reviewer needs to double check? - places where we pass `skip_authorization: true` ## Does this MR meet the acceptance criteria? - Tests - [x] Added for this feature/bug - [ ] All builds are passing - [ ] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html) - [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 it does - rebase it please) - [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) ## What are the relevant issue numbers? Fixes #23694 See merge request !7093
-
Guilherme Salazar authored
fix issues pointed out in !6527 add task completion status feature to CHANGELOG
-
Rémy Coutable authored
Merge branch '23872-members-of-group-that-has-project-access-getting-404-on-accessing-a-project-issue' into 'master' Fix project member access for group links Closes #23872. See merge request !7144
-
Stan Hu authored
Merge branch 'ee-1159-allow-permission-check-bypass-in-approve-access-request-service' into 'master' Allow Members::ApproveAccessRequestService to accept a new `:force` option ## What does this MR do? See the commit message. This is a backport of the EE fix for https://gitlab.com/gitlab-org/gitlab-ee/issues/1159: gitlab-org/gitlab-ee!830 See merge request !7168
-
Rémy Coutable authored
Fix CHANGELOG for GH import fixes See merge request !7173
-
Annabel Dunstone Gray authored
-
Sean McGivern authored
add "x of y tasks completed" on issuable Closes #22392 See merge request !6527
-
ido authored
While loading, the entire dropdown is greyed out. However, The focus is on the text input, so user can input text. Move the focus event to after loading finished to fix this.
-
Fatih Acet authored
Create cycle analytics bundle ## What does this MR do? Currently the cycle analytics file is being included in our application.js file & therefore including VueJS in application.js. This MR creates a cycle analytics bundle and only includes it on the cycle analytics page. See merge request !7176
-
Dmytro Zaporozhets (DZ) authored
Make internal api work with full repo path and name ## What does this MR do? Make internal api work with full repo path and name ## Why was this MR needed? So we can pass full repository path on filesystem from gitlab-shell instead of extracted one. We need this for nested groups support where project is can be nested under several groups. ## What are the relevant issue numbers? https://gitlab.com/gitlab-org/gitlab-ce/issues/2772 See merge request !7148
-
Fatih Acet authored
Only remove right connector of first build of last stage Only remove right connector of first build of last stage. Closes #23849 See merge request !7179
-
Closes #23926
-
Fatih Acet authored
Do not allow text input in dropdown while loading ## What does this MR do? It moves the focus event of the text input of a filterable dropdown to after loading of options is complete. After the fix, the user cannot edit the while it's greyed out and loading. ## Are there points in the code the reviewer needs to double check? ## Why was this MR needed? It fixes the bug in https://gitlab.com/gitlab-org/gitlab-ce/issues/23496. ## Screenshots (if relevant)  ## What are the relevant issue numbers? Fixes #23496 See merge request !7054
-
Fatih Acet authored
Fixed sticky MR tabs positioning when sidebar is pinned ## What does this MR do? The sticky MR tabs where positioned underneath the pinned sidebar. This fixes that by accounting for the size of the pinned nav. ## Screenshots (if relevant)  ## What are the relevant issue numbers? Closes #23926 See merge request !7167
Showing
- .gitlab-ci.yml 1 addition, 1 deletion.gitlab-ci.yml
- CHANGELOG.md 15 additions, 2 deletionsCHANGELOG.md
- Gemfile 3 additions, 0 deletionsGemfile
- Gemfile.lock 5 additions, 1 deletionGemfile.lock
- app/assets/javascripts/boards/stores/boards_store.js.es6 2 additions, 1 deletionapp/assets/javascripts/boards/stores/boards_store.js.es6
- app/assets/javascripts/cycle_analytics/cycle_analytics_bundle.js.es6 0 additions, 0 deletions...javascripts/cycle_analytics/cycle_analytics_bundle.js.es6
- app/assets/javascripts/gl_dropdown.js 8 additions, 3 deletionsapp/assets/javascripts/gl_dropdown.js
- app/assets/javascripts/issue.js 5 additions, 1 deletionapp/assets/javascripts/issue.js
- app/assets/javascripts/merge_request.js 5 additions, 1 deletionapp/assets/javascripts/merge_request.js
- app/assets/stylesheets/framework/lists.scss 1 addition, 1 deletionapp/assets/stylesheets/framework/lists.scss
- app/assets/stylesheets/framework/sidebar.scss 12 additions, 0 deletionsapp/assets/stylesheets/framework/sidebar.scss
- app/assets/stylesheets/pages/pipelines.scss 1 addition, 2 deletionsapp/assets/stylesheets/pages/pipelines.scss
- app/controllers/concerns/service_params.rb 1 addition, 1 deletionapp/controllers/concerns/service_params.rb
- app/controllers/projects/issues_controller.rb 1 addition, 1 deletionapp/controllers/projects/issues_controller.rb
- app/controllers/projects/merge_requests_controller.rb 1 addition, 1 deletionapp/controllers/projects/merge_requests_controller.rb
- app/controllers/projects_controller.rb 2 additions, 0 deletionsapp/controllers/projects_controller.rb
- app/finders/labels_finder.rb 7 additions, 8 deletionsapp/finders/labels_finder.rb
- app/helpers/issuables_helper.rb 8 additions, 0 deletionsapp/helpers/issuables_helper.rb
- app/models/ci/pipeline.rb 6 additions, 6 deletionsapp/models/ci/pipeline.rb
- app/models/commit_status.rb 6 additions, 6 deletionsapp/models/commit_status.rb
... | @@ -161,6 +161,9 @@ gem 'connection_pool', '~> 2.0' | ... | @@ -161,6 +161,9 @@ gem 'connection_pool', '~> 2.0' |
# HipChat integration | # HipChat integration | ||
gem 'hipchat', '~> 1.5.0' | gem 'hipchat', '~> 1.5.0' | ||
# JIRA integration | |||
gem 'jira-ruby', '~> 1.1.2' | |||
# Flowdock integration | # Flowdock integration | ||
gem 'gitlab-flowdock-git-hook', '~> 1.0.1' | gem 'gitlab-flowdock-git-hook', '~> 1.0.1' | ||
... | ... |
File moved