1. 16 Dec, 2016 34 commits
  2. 15 Dec, 2016 6 commits
    • Achilleas Pipinellis's avatar
      Merge branch 'docs/add-okta-auth' into 'master' · b562633e
      Achilleas Pipinellis authored
      Add Okta authentication documentation
      
      Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/14122
      
      See merge request !8104
      b562633e
    • Allison Whilden's avatar
      fb4d763c
    • Alfredo Sumaran's avatar
      Fix eslint errors · 958a499a
      Alfredo Sumaran authored
      958a499a
    • Achilleas Pipinellis's avatar
      Merge branch 'ha_docs_auto_migrate_false' into 'master' · 58597bf5
      Achilleas Pipinellis authored
      Add `gitlab_rails['auto_migrate'] = false` to HA docs for Redis/PG [ci skip]
      
      ## What does this MR do?
      
      In a high availability configuration, the Redis and PostgreSQL nodes
      should not attempt to run database migrations. In fact, trying will
      result in errors about not providing a database password. To
      prevent errors and confusion, add this configurtion to these nodes'
      `gitlab.rb` file.
      
      See merge request !8112
      58597bf5
    • Kamil Trzciński's avatar
      Merge branch... · 026cef7a
      Kamil Trzciński authored
      Merge branch '25144-gitlab-ce-mattermost-slash-command-for-issue-create-needs-better-documentation' into 'master'
      
      Resolve "gitlab-ce mattermost slash command for issue create needs better documentation"
      
      ## What does this MR do?
      
      Updates the documentation and the <kbd>help</kbd> command to be clearer, having the keys used to add a newline in chat clients (both Mattermost and Slack). 
      
      ## Are there points in the code the reviewer needs to double check?
      
      * Are the available commands (via <kbd>help</kbd>) being formatted as `<code>` ?
      
      ## Why was this MR needed?
      
      `\n` represents a new line character and doesn't communicate how the user should input the command. Also, to be correct, the documentation should use `<kbd>` instead of `<code>` for user input ([see HTML5 specification](https://www.w3.org/TR/html5/text-level-semantics.html#the-kbd-element))
      
      ## Screenshots (if relevant)
      
      | Mattermost | Docs |
      | --- | --- |
      | ![image](/uploads/539526a14bfd551b7e732dd96c5b7581/image.png) | ![image](/uploads/e3eb099f86c5a32ce3b8954e72c29848/image.png) |
      
      ## Does this MR meet the acceptance criteria?
      
      - [x] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added
      - [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
      - Tests
        - [ ] All builds are passing
      
      ## What are the relevant issue numbers?
      
      Closes #25144
      
      See merge request !7850
      026cef7a
    • Fatih Acet's avatar
      Merge branch '24877-bulk-edit-only-keeps-common-labels-when-searching' into 'master' · b01a830a
      Fatih Acet authored
      Improve bulk assignment
      
      This MR improves current implementation of Label dropdown when used for bulk assignment on issuable pages (/:namespace/:project/issues, /:namespace/:project/merge_requests)
      
      Previously this dropdown relied on `<input>` tags to get its active items and also to calculate items with indeterminate state.
      
      Relying on `<input>` tags is not enough when we want to set/get multiple states on a dropdown.
      
      For this case we want to get/set:
      
      - Marked items 
      - Unmarked items that were initially marked
      - Unmarked items that were initially indeterminate
      - Items with indeterminate state.
      
      This MR makes the Label dropdown to save its own state as `data` so it will be easy to get and set whatever state we want no matter if the dropdown is filtering which is the issue that I initially wanted to solve as you can see in the following gif.
      
      **Before** 
      ![2016-12-07_11.44.48](/uploads/cb697161b8b39cdee72fdbb95a531100/2016-12-07_11.44.48.gif)
      
      **After**
      ![2016-12-07_11.32.43](/uploads/338255a302de0dd1367474f33232d2a3/2016-12-07_11.32.43.gif)
      
      As you can see in the first gif the `bug` label is removed from the selected issues but the `enhancement` label should set but the `critical` should be kept. This is fixed on the next gif.
      
      Fixes #24877
      
      See merge request !7765
      b01a830a