add hint how to use ssh access to remote mirror repository #952
derReparierer/docs:derreparierer-patch-1 into next Preview ready: https://forgejo.codeberg.page/@docs_pull_952/
@ -83,3 +83,3 @@
This feature is only available if Forgejo is able to find the `ssh` executable.
To use SSH as authentication method, select the **Use SSH authentication** option in the authorization tab when adding a new push mirror.
To use SSH as authentication method, select the **Use SSH authentication** option in the authorization tab when adding a new push mirror. Make sure to use ssh conform URLs for **Git Remote Repository URL**, which is e.g. `git@github.com:<your_github_group>/<your_github_project>.git` for GitHub (differs to the default authorization approach as mentioned above).
I don't see the need to use github.com instead of forgejo.org or example.com as example URL. Also the sentence should be moved to its own line.
moved to new line
I have tested this for GitHub, so this example is used. Currently i can not verify for Forgejo.
It works for Forgejo.
The lint error is related: it is a trailing space.
Thanks!
Broken links or missing content
Changes which should be backported to the v1.19 docs
Archived
Changes which should be backported to the v1.20 docs
Archived
Changes which should be backported to the v1.21 docs
Archived
Automated backport to v10.0
Archived
Automated backport to v11.0
Automated backport to v12.0
Archived
Automated backport to v13.0
Automated backport to v14.0
Automated backport to the v7.0 docs
Archived
Automated backport to the v8.0 docs
Archived
Automated backport to the v9.0 docs
Archived
This issue is suitable for "drive-by contributors" wanting to contribute for the first time, and fixing it should be straightforward.
Tooling and processes for maintaining the docs
Content to be added to the documentation
Archived
Requires input about accessibility features, likely involves user testing.
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
Instance-wide configuration, authentication and other admin-only needs.
How to deal with errors in the application and write helpful error messages.
How filter and search is being worked with.
The issue might be inspiring for future design work.
AGit, fork-based and new Git workflow, PR creation etc
Active research about Labels
Moderation Featuers for Admins are undergoing active User Research
Use this label to let the User Research team know their input is requested.
Research on how users should know what to do next.
Text rendering, markup languages etc
Active research about the New Repo dialog.
The repo sections, disabling them and the "Add more" button.
How to structure in-app settings in the future?
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?