| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of requiring one separate document for every version (which is
created by release managers), we now use a single document for both
Community Edition and Enterprise Edition. This allows developers to add
guidelines right away, instead of release managers having to determine
what to add.
Version specific upgrading instructions are placed in a separate
section. This prevents instructions from lingering around for many
versions should a developer forget to remove them. This also ensures
that all instructions are kept in a single place, instead of being
spread across different documents.
A minor downside is that CE and EE guidelines now live in the same
document, which could cause merge conflicts. Since we are working
towards a single codebase, this should only be an issue until we merge
the codebases together; something we expect to do in the coming months.
This commit also removes all old upgrading instructions, but these can
still be accessed using Git branch specific URLs (included in the
updating README).
|
| |\
| |
| |
| |
| | |
Resolve Markdown unordered lists not conforming to styleguide
See merge request gitlab-org/gitlab-ce!23037
|
| | |
| |
| |
| | |
- Also makes other minor Markdown fixes that were near the main fixes.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the administration page for web terminals add a new `Security`
section explaining how the interactive web terminals are secured between
GitLab and gitlab-runner.
This section is under administration instead of
`doc/ci/interactive_web_terminal` because the administrators of the
GitLab instance would be mostly interested in this, whilst
`doc/ci/interactive_web_terminal` are interested in how the feature
works.
closes https://gitlab.com/gitlab-org/gitlab-ce/issues/52681
|
| |
|
|
|
|
| |
This integration no longer works and does not appear to be supported.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/39697
|
| | |
|
| | |
|
| |
|
|
| |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Add documentation for PlantUML in reStructuredText
See merge request !13900
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Fix broken links to docs
See merge request !9022
|
| | |
| |
| |
| | |
[ci skip]
|
| |/
|
|
|
| |
Store the value in application settings.
Expose the value to Workhorse.
|
| |\
| |
| |
| |
| | |
Refactor integrations page documentation
See merge request !8966
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
| |
Allow rendering of PlantUML diagrams in Markdown documents using fenced blocks:
```plantuml
Bob -> Sara : Hello
Sara -> Bob : Go away
```
Closes: #4048
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This MR enables rendering of PlantUML diagrams in Asciidoc documents. To add a
PlantUML diagram all we need is to include a plantuml block like:
```
[plantuml, id="myDiagram", width="100px", height="100px"]
--
bob -> alice : ping
alice -> bob : pong
--
```
The plantuml block is substituted by an HTML img element with *src* pointing to
an external PlantUML server.
This MR also add a PlantUML integration section to the Administrator -> Settings
page to configure the PlantUML rendering service and to enable/disable it.
Closes: #17603
|
| | |
|
| | |
|
| |
|
|
| |
Signed-off-by: Sonmez Kartal <sonmez@koding.com>
|
| |
|
