Enabling linkattrs explicitly on doc pages having external links
Asciidoc may fail to render link attributes for external links supposed to open in a new window correctly. This change adds :linkattrs: to the beginning of such files to force parsing link attributes correctly. Bug: Issue 12068 Change-Id: If18be60de646ff78f672239dd4fa435fd4fd92ab
This commit is contained in:
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Access Controls
|
||||
|
||||
Access controls in Gerrit are group based. Every user account is a
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Backup
|
||||
|
||||
A Gerrit Code Review site contains data that needs to be backed up regularly.
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= commit-msg Hook
|
||||
|
||||
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= The refs/for namespace
|
||||
|
||||
When pushing a new or updated commit to Gerrit, you push that commit using a
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Accounts
|
||||
|
||||
== Overview
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Configuration
|
||||
|
||||
== File `etc/gerrit.config`
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
== Gitweb Integration
|
||||
|
||||
Gerrit Code Review can manage and generate hyperlinks to gitweb,
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Hooks
|
||||
|
||||
Gerrit does not run any of the standard git hooks in the repositories
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Mail Templates
|
||||
|
||||
Gerrit uses link:https://developers.google.com/closure/templates/[Closure Templates,role=external,window=_blank]
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Plugins
|
||||
|
||||
The Gerrit server functionality can be extended by installing plugins.
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Single Sign-On Security
|
||||
|
||||
Gerrit supports integration with some types of single sign-on
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Building with Bazel
|
||||
|
||||
[[installation]]
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Contributor License Agreement
|
||||
|
||||
In order to link::dev-community.html#how-to-contribute[contribute] to
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Community
|
||||
|
||||
Gerrit is developed as a
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Contributing
|
||||
|
||||
[[cla]]
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Core Plugins
|
||||
|
||||
[[definition]]
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Crafting Changes
|
||||
|
||||
Here are some hints as to what approvers may be looking for
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - System Design
|
||||
|
||||
== Objective
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - End to end load tests
|
||||
|
||||
This document provides a description of a Gerrit load test scenario implemented using the link:http://gatling.io[`Gatling`] framework.
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Eclipse Setup
|
||||
|
||||
This document is about configuring Gerrit Code Review into an
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Inspector
|
||||
|
||||
== NAME
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - IntelliJ IDEA Setup
|
||||
|
||||
== Prerequisites
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Plugin Lifecycle
|
||||
|
||||
Most of the plugins are hosted on the same instance as the
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Plugin Development
|
||||
|
||||
The Gerrit server functionality can be extended by installing plugins.
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Development Processes
|
||||
|
||||
[[project-governance]]
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review: Developer Setup
|
||||
|
||||
To build a developer instance, you'll need link:https://bazel.build/[Bazel,role=external,window=_blank] to
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Deploy Gerrit Artifacts
|
||||
|
||||
[[deploy-configuration-setting-maven-central]]
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Making a Snapshot Release of JGit
|
||||
|
||||
This step is only necessary if we need to create an unofficial JGit
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Making a Release of a Gerrit Subproject
|
||||
|
||||
[[make-snapshot]]
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Making a Gerrit Release
|
||||
|
||||
[NOTE]
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Supporting Roles
|
||||
|
||||
As an open source project Gerrit has a large community of people
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Starter Projects
|
||||
|
||||
We have created a
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= change ... closed
|
||||
|
||||
With this error message Gerrit rejects to push a commit or submit a
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= commit xxxxxxx: Change-Id must be in message footer
|
||||
|
||||
With this error message, Gerrit rejects a push of a commit to a project
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= contains banned commit ...
|
||||
|
||||
With this error message Gerrit rejects to push a commit that is
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= ... has duplicates
|
||||
|
||||
With this error message Gerrit rejects to push a commit if its commit
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= invalid author
|
||||
|
||||
For every pushed commit Gerrit verifies that the e-mail address of
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= invalid Change-Id line format in commit message footer
|
||||
|
||||
With this error message Gerrit rejects to push a commit if its commit
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= invalid committer
|
||||
|
||||
For every pushed commit Gerrit verifies that the e-mail address of
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= commit xxxxxxx: missing Change-Id in message footer
|
||||
|
||||
With this error message Gerrit rejects to push a commit to a project
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= commit xxxxxxx: missing subject; Change-Id must be in message footer
|
||||
|
||||
With this error message Gerrit rejects to push a commit to a project
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= commit xxxxxxx: multiple Change-Id lines in message footer
|
||||
|
||||
With this error message Gerrit rejects to push a commit if the commit
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= no new changes
|
||||
|
||||
With this error message Gerrit rejects to push a commit if the pushed
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= non-fast forward
|
||||
|
||||
With this error message Gerrit rejects a push if the remote branch can't
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= you are not allowed to upload merges
|
||||
|
||||
With this error message Gerrit rejects to push a merge commit if the
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Permission denied (publickey)
|
||||
|
||||
With this error message an SSH command to Gerrit is rejected if the
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Push fails due to commit message
|
||||
|
||||
If Gerrit rejects pushing a commit it is often the case that there is
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= same Change-Id in multiple changes
|
||||
|
||||
With this error message Gerrit rejects to push a commit if it
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Upload denied for project ...
|
||||
|
||||
With this error message Gerrit rejects to push a commit if the
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review for Git
|
||||
|
||||
== Quickstarts
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - J2EE Installation
|
||||
|
||||
== Description
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Standalone Daemon Installation Guide
|
||||
|
||||
[[prerequisites]]
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Basic Gerrit Walkthrough -- For GitHub Users
|
||||
|
||||
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Working with Gerrit: An example
|
||||
|
||||
To understand how Gerrit works, let's follow a change through its entire
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Project Owner Guide
|
||||
|
||||
This is a Gerrit guide that is dedicated to project owners. It
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review Product Overview
|
||||
|
||||
Gerrit Code Review is a web-based code review tool built on
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Use Gerrit to Be a Rockstar Programmer
|
||||
|
||||
== Overview
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= User Guide
|
||||
|
||||
This is a Gerrit guide that is dedicated to Gerrit end-users. It
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Quickstart for Installing Gerrit on Linux
|
||||
|
||||
This content explains how to install a basic instance of Gerrit on a Linux
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - NoteDb Backend
|
||||
|
||||
NoteDb is the next generation of Gerrit storage backend, which replaces the
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - PolyGerrit Plugin Development
|
||||
|
||||
CAUTION: Work in progress. Hard hat area. Please
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - PolyGerrit Plugin Development
|
||||
|
||||
CAUTION: Work in progress. Hard hat area. Please
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - PolyGerrit Plugin Styling
|
||||
|
||||
== Plugin styles
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= MigrateAccountPatchReviewDb
|
||||
|
||||
== NAME
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Prolog Submit Rules Cookbook
|
||||
|
||||
[[SubmitRule]]
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Quota
|
||||
|
||||
Gerrit does not provide out of the box quota enforcement. However, it does
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - /accounts/ REST API
|
||||
|
||||
This page describes the account related REST endpoints.
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - /changes/ REST API
|
||||
|
||||
This page describes the change related REST endpoints.
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - /projects/ REST API
|
||||
|
||||
This page describes the project related REST endpoints.
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - REST API
|
||||
|
||||
Gerrit Code Review comes with a REST like API available over HTTP.
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Creating and Editing Changes in the Gerrit Web Interface
|
||||
|
||||
== Overview
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Request Tracing
|
||||
|
||||
[[on-demand]]
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Review UI
|
||||
|
||||
Reviewing changes is an important task and the Gerrit Web UI provides
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Searching Changes
|
||||
|
||||
== Default Searches
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Signed-off-by Lines
|
||||
|
||||
[NOTE]
|
||||
|
@@ -1,3 +1,4 @@
|
||||
:linkattrs:
|
||||
= Gerrit Code Review - Uploading Changes
|
||||
|
||||
Gerrit supports three methods of uploading changes:
|
||||
|
Reference in New Issue
Block a user