mirror of
https://github.com/abapGit/abapGit.git
synced 2025-04-30 20:03:20 +08:00
fix pages build (#4196)
This commit is contained in:
parent
24649f4b71
commit
5e629f19a7
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Global settings
|
||||
category: setup
|
||||
order: 05
|
||||
order: 100
|
||||
---
|
||||
|
||||
Global settings in abapGit are valid system-wide and for all users. You can maintain the settings from the repository list or repository view by selecting "Settings > Global".
|
||||
|
@ -18,9 +18,9 @@ Note: Global settings are relevant for online projects, only.
|
|||
If your server is behind a proxy, you can maintain the proxy host and port here. Do not enter any "http://" or "https://" prefix for the proxy host. Just enter the host name
|
||||
or its IP address.
|
||||
|
||||
If your proxy requires you to login, set the proxy authentication flag. Then abapGit will prompt you for your proxy user and password, when an online connection is required.
|
||||
If your proxy requires you to login, set the proxy authentication flag. Then abapGit will prompt you for your proxy user and password, when an online connection is required.
|
||||
|
||||
In case the proxy should not be used for all repositories, exceptions can be maintained. Enter each exception on a separate line. Patterns are allowed,
|
||||
In case the proxy should not be used for all repositories, exceptions can be maintained. Enter each exception on a separate line. Patterns are allowed,
|
||||
for example "*.sap.internal*".
|
||||
|
||||
## Commit Message Settings
|
||||
|
@ -28,7 +28,7 @@ for example "*.sap.internal*".
|
|||
Each commit to an online repository requires a commit message. The corresponding settings define the maximum length for the comment (message header) and body. Defaults are set
|
||||
to 50/72 according to the "[Rule of Well Formed Git Commit Messages](https://www.midori-global.com/blog/2018/04/02/git-50-72-rule)".
|
||||
|
||||
You can also maintain a default for the comment. Variables $OBJECT and $FILE will be replaced by the number of objects or files contained in the commit.
|
||||
You can also maintain a default for the comment. Variables $OBJECT and $FILE will be replaced by the number of objects or files contained in the commit.
|
||||
|
||||
## Development Internal Settings
|
||||
|
||||
|
@ -36,9 +36,9 @@ Note: These settings are only available when using the [Development Version](htt
|
|||
|
||||

|
||||
|
||||
### Enable Critical Unit Tests
|
||||
### Enable Critical Unit Tests
|
||||
The developer version of abapGit might contain unit tests that impact system settings (like creating/deleting test objects). By default, these test are disabled.
|
||||
|
||||
### Enable Experimental Features
|
||||
### Enable Experimental Features
|
||||
There might be features that are not completely implemented or tested yet but already included in the developer version. By default, these features are disabled.
|
||||
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Personal settings
|
||||
category: setup
|
||||
order: 08
|
||||
order: 200
|
||||
---
|
||||
|
||||
Personal settings in abapGit are valid only for the logged on user. You can maintain the
|
||||
|
@ -14,26 +14,26 @@ Note: Personal settings are relevant all of your repositories.
|
|||

|
||||

|
||||
|
||||
## Startup
|
||||
## Startup
|
||||
|
||||
If you turn on "Show Last Opened Repository", abapGit will jump directly to the repository that you worked on last.
|
||||
If you turn on "Show Last Opened Repository", abapGit will jump directly to the repository that you worked on last.
|
||||
|
||||
## User Interface
|
||||
|
||||
You can switch the theme for abapGit between several choices: Default, Dark, and Belize. Alternatively, you can select "Synced with SAP GUI" to use the same theme
|
||||
you are using for SAP GUI (availability depends on SAP GUI release).
|
||||
you are using for SAP GUI (availability depends on SAP GUI release).
|
||||
|
||||
The size of icons can be changed using "icon scaling".
|
||||
The size of icons can be changed using "icon scaling".
|
||||
|
||||
"List Size" defines the maximum number of items shown in a list. If there are more items, then abapGit start paging.
|
||||
|
||||
## Interaction
|
||||
## Interaction
|
||||
|
||||
Typically, when objects are changed, the system will display a popup to confirm the activation of objects. This gives the change to address syntax errors, for example.
|
||||
If you want objects to be activated automatically, select "Activate Objects Without Popup". If there are syntax errors, abapGit will indicate this with an icon next to
|
||||
the objects in the repository view.
|
||||
|
||||
If you are using ABAP Development Tools (ADT) in Eclipse, we recommend to turn on "Enable Jump to ABAP Development Tools". Clicking on objects names in abapGit will then
|
||||
If you are using ABAP Development Tools (ADT) in Eclipse, we recommend to turn on "Enable Jump to ABAP Development Tools". Clicking on objects names in abapGit will then
|
||||
open the object in ADT (if available).
|
||||
|
||||
"Enable Vimium-like Link Hints" and "Key to Activate Link Hints" provide a feature similarly to the [Vimium browser](https://vimium.github.io/). After pressing the
|
||||
|
@ -41,7 +41,7 @@ activation key (default "f"), abapGit will uses a clever highlighting method to
|
|||
|
||||

|
||||
|
||||
## System Resources
|
||||
## System Resources
|
||||
|
||||
By default and if sufficient system resources are available, abapGit will use parallel processing to serialize objects of a repository. You can disable parallel processing
|
||||
with this setting. Note: Use this setting in case you need to debug a serializer class.
|
||||
|
|
Loading…
Reference in New Issue
Block a user