-
Notifications
You must be signed in to change notification settings - Fork 4
adapt account creation doc #27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Nils-Magnus
left a comment
There was a problem hiding this 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
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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! |
There was a problem hiding this comment.
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. | ||
|
|
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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
|
recheck |
|
Build succeeded. ✔️ otc-tox-docs SUCCESS in 10m 20s |
This PR is created on base of #26 to reimplement it on top of current master branch ignoring all not relevant local commits: