Andrew Winata authored 5 years ago and Evan Read committed 5 years ago

Also another factor of consideration for
runner server requirements.

* Adjust opened issues count in the milestone burndown chart
to match current opened issues in the milestone.
* Fix completion rate calculation to include milestones only.

Nikolay Samokhvalov authored 5 years ago and Evan Read committed 5 years ago

Currently, the field used to fill the contents is called "code".
Also "visibility" is now required.

This gem allows you to get the `EXPLAIN ANALYZE` query plan, directly
from the Rails console.

The gem is installed with `require: false`, but if it was loaded on
launch, this would be it's memory load:

```
TOP: 145.3086 MiB
  rails/all: 22.4844 MiB
  ...
  activerecord-explain-analyze: 2.9648 MiB
    active_record/connection_adapters/postgresql_adapter: 2.9648 MiB
      pg: 2.9648 MiB
        pg_ext: 2.9648 MiB
  ...
```

This is an initiative to ensure all documentation complies completely
with the Documentation Style Guide section "Documentation is the single
source of truth (SSOT)" according to this epic
https://gitlab.com/groups/gitlab-org/-/epics/1280.

In particular, the changes of this commit touch all files under
doc/install/. Most notably:

- install/redis.md:
        Redirect to Redis section of install guide.

- install/pivotal/index.md:
        Changed its content to reflect the current status, which is no
        longer supported (since 2017!).

- install/google-protobuf.md:
        Incorporated inside installation.md under the troubleshooting section.

- install/openshift_and_gitlab.md:
        Clarified that this guide is no longer relevant. We might want to
        redirect to the Chart docs in the future.

- install/structure.md:
        Incorporated inside installation.md under its own section.

- install/kubernetes/index.md:
        Redirected to https://docs.gitlab.com/charts

Add a few useful links for those who want to learn more about
databases and database performance.

The lack of indentatioin is causing the markdown parser to get confused
and formating it wrong.

We can query namespaces, and nested projects.

Projects now exposes statistics

The previous examples did work however they had a problem when the
bin/setup script installed a different bundler version than the one in
your Gemfile.lock.  It is safer to use `/bin/herokuish procfile exec` to
get access to all the environment already installed for your application
instead of installing bundler again.

This couples the code that transitions the `MergeRequest#merge_status`
and refs/merge-requests/:iid/merge ref update.

In general, instead of directly telling `MergeToRefService` to update
the merge ref, we should rely on `MergeabilityCheckService` to keep
both the merge status and merge ref synced. Now, if the merge_status is
`can_be_merged` it means the merge-ref is also updated to the latest.

We've also updated the logic to be more systematic and less user-based.

This extends POST#:id/repository/commits to allow the optional parameter
`:start_project`, which will allow targeting other projects besides the
one derived from `:id`.

Resolves https://gitlab.com/gitlab-org/gitlab-ce/issues/50850

Charlie Ablett authored 5 years ago and Charlie Ablett committed 5 years ago

- Comply doc with guidelines
- Improve tests for readability and completeness
- Separate out phases visually with newlines
- Add `format_message` test
- test readability
- code and test structure/styling
- static query analyzers
- call `as_json` on `provided_variables`
- add exception handling

This sets up all the basics for importing Phabricator tasks into
GitLab issues.

To import all tasks from a Phabricator instance into GitLab, we'll
import all of them into a new project that will have its repository
disabled.

The import is hooked into a regular ProjectImport setup, but similar
to the GitHub parallel importer takes care of all the imports itself.

In this iteration, we're importing each page of tasks in a separate
sidekiq job.

The first thing we do when requesting a new page of tasks is schedule
the next page to be imported. But to avoid deadlocks, we only allow a
single job per worker type to run at the same time.

For now we're only importing basic Issue information, this should be
extended to richer information.