docs: contributing to abapGit #1402 (#1420)

* link to the section in docs.abapgit.org

https://github.com/larshp/abapGit/issues/1402

* add doc page contributing to abapGit

https://github.com/larshp/abapGit/issues/1402

* Contributing to abapGit section other

https://github.com/larshp/abapGit/issues/1402

* moved to others 

https://github.com/larshp/abapGit/issues/1402

* link changed to section other 

https://github.com/larshp/abapGit/issues/1402
This commit is contained in:
Johannes Konings 2018-05-27 16:28:48 +02:00 committed by Lars Hvam
parent 0aecdf7255
commit 998d89b314
2 changed files with 22 additions and 13 deletions

View File

@ -33,16 +33,4 @@ https://guides.github.com/activities/contributing-to-open-source/
## Building/Creating a PR
1: Install the development version of abapGit by cloning the repository using an online repository, or downloading the zip file and installing it using an offline repository.
2: The abapGit report installed in your system will now consist of multiple classes
3: Do the required changes to classes and/or main program
4: Create the pull request with the changes
5: After the pull request is merged, abapmerge will automatically run to build the report version of abapGit.
Every time a commit is pushed to the master branch, https://travis-ci.org/ will be triggered to perform the build. It will use [abapmerge](https://github.com/larshp/abapmerge) to merge all the includes into a single file, the build can be downloaded from https://raw.githubusercontent.com/abapGit/build/master/zabapgit.abap
Alternatively, use the GitHub webinterface to change the files and submit a pull request.
Building/Creating a PR is described here: http://docs.abapgit.org/other-contributing-abapGit.html

View File

@ -0,0 +1,21 @@
---
title: Contributing to abapGit
category: other
order: 90
---
*******************************
1: Install the development version of abapGit by cloning the repository using an online repository, or downloading the zip file and installing it using an offline repository.
2: The abapGit report installed in your system will now consist of multiple classes
3: Do the required changes to classes and/or main program
4: Create the pull request with the changes
5: After the pull request is merged, abapmerge will automatically run to build the report version of abapGit.
Every time a commit is pushed to the master branch, https://travis-ci.org/ will be triggered to perform the build. It will use [abapmerge](https://github.com/larshp/abapmerge) to merge all the includes into a single file, the build can be downloaded from https://raw.githubusercontent.com/abapGit/build/master/zabapgit.abap
Alternatively, use the GitHub webinterface to change the files and submit a pull request.