Article directory
I. Overview
The installation is relatively simple. In order to use it well, we need to briefly understand its interface functions and have an overall understanding. We cannot operate blindly or mess around.
2. UI layout
abapGit user interface is based on HTML. Each page is divided into four parts: header, title, content, and footer. Students who understand HTML page development should be very aware of this layout style: top, header, content, and footer.
2.1 Top of page
At the top of every page, abapGit displays its logo and current page title on the left, and optional menu items on the right.
This part is frozen in the window. When there is a lot of content, scroll the content down and it will still remain at the top.
2.2 Title
Repository-related pages in abapGit contain a header that contains basic Repository-warehouse information and some useful function buttons.
Different functions will have different displays. For example, after clicking in the Repository in offline mode: After clicking in
the Repository in online mode
, the head-up display will appear.
2.3 Page content
How the area between the header and footer is filled differently depending on the selected page or command. Some pages, such as the repository list and repository view, contain additional menu bars. For pages that contain input forms, use the top menu bar to switch between forms (such as tabs), and use the bottom row of buttons to select commands.
When selecting different Repositories, the content will change and the title will also change.
2.4 Footer content
On every page, the same footer content appears at the bottom of the page, containing sponsored link buttons, version information, and JavaScript status.
3. UI function settings
3.1 Global settings
Global settings in abapGit are system-wide and valid for all users. You can maintain settings in the repository list or repository view by selecting Settings > Global.
After clicking, as shown in the figure below, global settings are only relevant to online projects.
3.2 Personal settings
Personal settings are only valid for logged in users, but are related to all personal repositories.
3.3Repository settings
The folder creation logic is explained separately here. You can set the starting root folder name, which defaults to src.
abapGit follows three folder logics: "Prefix", "Full" and "Mixed".
#PrefixA
package name must include its parent package name as a prefix. example:
Valid package prefixes:
ZFOO
ZFOO_BAR
ZFOO_BAR_QUX
This will produce the following folder structure:
/src
/src/bar
/src/bar/qux
Invalid package prefix:
ZFOO
ZBAR
folder logic PREFIX allows repositories to be installed into different parent packages (in different systems). This can even be in a local package ($*), in which case no transport order is required.
#FULL
accepts any package name.
ZBASE
ZSOMETHING
ZHELLO
This will produce the following folder structure:
/src
/src/zsomething
/src/zsomething/zhello
folder logic FULL Forces the repository to be installed into a package with the exact same name. Note that this may be problematic for contributors on systems that want to use a specific prefix for package names.
#MIXEDFolder
logicMIXED combines PREFIX and FULL. The root package name will be used as a prefix for all sub-packages, but the package names will not be concatenated recursively. This will allow the use of distinctive logical package names.
Package hierarchy example:
ZBASE
ZBASE_ZFOO
ZBASE_ZBAR
ZBASE_ZSUB_PACK_WITH_LONG_NAME
This will produce the following folder structure:
/src
/src/zfoo
/src/zfoo/zbar
/src/zfoo/zbar/zsub_pack_with_long_name