marmulle/internal-documentation
1
0
Fork 0
forked from docs/internal-documentation
Code Pull Requests Activity

Update 'doc/source/helpcenter/helpcenter_training/faq/how_to_update_landing_page.rst'

Browse Source
This commit is contained in:
Muller, Martin 2024-02-22 20:00:37 +00:00
parent a494045102
commit c8319629b2
1 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
doc/source/helpcenter/helpcenter_training/faq/how_to_update_landing_page.rst
View File

@ -6,16 +6,16 @@ How to update landing page
Mark service as depricated Mark service as depricated
.. image:: training_images/storage_component_overview.png .. image:: faq_images/storage_component_overview.png
:target: training_images/storage_component_overview.png :target: faq_images/storage_component_overview.png
:alt: storage_component_overview :alt: storage_component_overview
1)**Create fork on gitea** 1)**Create fork on gitea**
You need to create fork only in case you don’t have existing already You need to create fork only in case you don’t have existing already
.. image:: traininig_images/infra_otc_metadata.png .. image:: faq_images/infra_otc_metadata.png
:target: traininig_images/infra_otc_metadata.png :target: faq_images/infra_otc_metadata.png
:alt: infra_otc_metadata :alt: infra_otc_metadata
https://gitea.eco.tsi-dev.otc-service.com/marmulle/otc-metadata/src/branch/main/otc_metadata/data/documents https://gitea.eco.tsi-dev.otc-service.com/marmulle/otc-metadata/src/branch/main/otc_metadata/data/documents
@ -56,34 +56,34 @@ In this case I was updating obs-swiftapi.yaml located in https://gitea.eco.tsi-d
After update file propose file changes. Name of branch or pull request should be as short as possible,but meaningful. After update file propose file changes. Name of branch or pull request should be as short as possible,but meaningful.
.. image:: traininig_images/propose_file_change.png .. image:: faq_images/propose_file_change.png
:target: traininig_images/propose_file_change.png :target: faq_images/propose_file_change.png
:alt: propose_file_change :alt: propose_file_change
5)**Create new pull request** 5)**Create new pull request**
Change destination branch into infra:main and click New Pull Request. Change destination branch into infra:main and click New Pull Request.
.. image:: traininig_images/gitea_new_pull_request.png .. image:: faq_images/gitea_new_pull_request.png
:target: traininig_images/gitea_new_pull_request.png :target: faq_images/gitea_new_pull_request.png
:alt: gitea_new_pull_request :alt: gitea_new_pull_request
Change destination branch into infra:main and click New Pull Request Change destination branch into infra:main and click New Pull Request
.. image:: traininig_images/gitea_new_pull_request2.png .. image:: faq_images/gitea_new_pull_request2.png
:target: traininig_images/gitea_new_pull_request2.png :target: faq_images/gitea_new_pull_request2.png
:alt: gitea_new_pull_request2 :alt: gitea_new_pull_request2
Once again - New Pull Request Once again - New Pull Request
.. image:: traininig_images/gitea_new_pull_request3.png .. image:: faq_images/gitea_new_pull_request3.png
:target: traininig_images/gitea_new_pull_request3.png :target: faq_images/gitea_new_pull_request3.png
:alt: gitea_new_pull_request3 :alt: gitea_new_pull_request3
6)**New pull request approve, gate** 6)**New pull request approve, gate**
.. image:: traininig_images/gitea_new_pull_request_approve_gate.png .. image:: faq_images/gitea_new_pull_request_approve_gate.png
:target: traininig_images/gitea_new_pull_request_approve_gate.png :target: faq_images/gitea_new_pull_request_approve_gate.png
:alt: gitea_new_pull_request_approve_gate :alt: gitea_new_pull_request_approve_gate
7)**Delete branch** 7)**Delete branch**