[automatic-deployment] Add Automatic Deployment with GitHub Actions HowTo

[bastiW]

No description provided.

[nichtmax]

That's really cool, thank you!

[nichtmax]

Overall very nice! I'm not sure about Prepare Local Git Repository, do you even need this? You can edit files in the Github web interface and you're creating a new GitHub Repository later anyway. Then you write "Follow the instructions on the section …or push an existing repository from the command line", maybe just stick to one because of simplicity?

[nichtmax]

Just a few things ☺️

[bastiW]

@nichtmax

Overall very nice! I'm not sure about Prepare Local Git Repository, do you even need this? You can edit files in the Github web interface and you're creating a new GitHub Repository later anyway. Then you write "Follow the instructions on the section …or push an existing repository from the command line", maybe just stick to one because of simplicity?

I personally would never init a repository on the Github website. Only just small edits in documentation or readme files.

So I made it more consistent and explained how to create a new repository with the gh cli and how to push your local code to the remote.

[bastiW]

@nichtmax You can recheck this PR.

I was not sure about the correct section. Is this a HOWTO or a Guide. All other guides install something on the Uberspace. In my how-to I configure something on Github. I have chosen the how-to section.

What do I need to change to see the content of the .. author_list:: on the page?

[kimdiallo]

first of all, i love your guide! Automating deployments and thus preventing countless opportunities for manual errors or forgotten steps will help many people to avoid frustration in the first place. Thank you very much for that.
But that's precisely why it should be as simple as possible. So I hope you will forgive us for the many changes we have requested.

[kimdiallo]

Presumably not every reader will immediately realize that Isabell is referring to the default account here, and a repo does not necessarily have to be a website - so perhaps something like '' would be more appropriate?