Skip to content

Conversation

@gtema
Copy link
Contributor

@gtema gtema commented Aug 23, 2022

This PR is created on base of #26 to reimplement it on top of current master branch ignoring all not relevant local commits:

git checkout -b Nils-Magnus-toplevel_struct main
git pull [email protected]:Nils-Magnus/docs_on_docs.git toplevel_struct
git cherry-pick a1eb128c76e67a69cb3e3195f0831b527ff1bcc2
git checkout -b toplevel_struct
git push

@gtema gtema requested a review from Nils-Magnus August 23, 2022 06:36
Nils-Magnus
Nils-Magnus previously approved these changes Feb 3, 2024
Copy link
Contributor

@Nils-Magnus Nils-Magnus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Explains the necessary. Updates formatting. LGTM

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is mainly about re-syncing a few files.

8. Hit a “create an account”
9. You are almost done! GitHub just sent you a launch you that has to be entered to create the account ultimately. Note: The Code has to be entered manually and can´t be entered via “copy & paste”
10. You are asked with how many people you are working with and if you are a student or a teacher. This personalization can be skipped at the bottom of the Website. I would suggest skipping this step.
11. Congratulations you just created you GitHub account
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dropped this file without rstextension.

are a student or a teacher. This personalization can be skipped at
the bottom of the Website. I suggest skipping this step.

11. Congratulations! You just created your GitHub account!
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

... and fixing the right one with proper formatting.

of the overall documentation. All changes are recorded and archived,
so changes can be rolled back, and audit trails are available even for
the tiniest change.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reformatting

recommended, but other setups are also possible.
or several Squad members (or external contributors, if suitable).
Typically, one documentation lead and a deputy are recommended, but
other setups are also possible.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reformatting


The architecture, process, and implementation of the Helpcenter 3.0
was initiated by the Ecosystem Squad. It was presented to the Product
Owner Community and during the XXXXXXXXXXX meeting/call/board. It was
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be updated in a later PR

change_proposal_process
reviewer
approver
account_creation
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

adding this file to the main page

@Nils-Magnus
Copy link
Contributor

recheck

@SebastianGode SebastianGode added the gate Merge PR label Feb 6, 2024
@otc-zuul
Copy link

otc-zuul bot commented Feb 6, 2024

@otc-zuul otc-zuul bot merged commit 8be8399 into main Feb 6, 2024
@otc-zuul otc-zuul bot deleted the toplevel_struct branch February 6, 2024 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gate Merge PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants