mirror of
https://codeberg.org/forgejo/docs.git
synced 2024-11-21 17:36:59 -05:00
docs: v1.20: sync Codeberg 2887826c38b3aae76a18f0696b40217b429226ce
This commit is contained in:
parent
121a25e25e
commit
c9e4722b3f
5 changed files with 7 additions and 5 deletions
|
@ -2,7 +2,7 @@
|
|||
layout: '~/layouts/Markdown.astro'
|
||||
title: 'Email Settings'
|
||||
license: 'CC-BY-SA-4.0'
|
||||
origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/95574213ea1b57f207f60a12557ffbfc349ee274/content/getting-started/email-settings.md'
|
||||
origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/2887826c38b3aae76a18f0696b40217b429226ce/content/getting-started/email-settings.md'
|
||||
---
|
||||
|
||||
By default, Forgejo will send notifications to your registered email addresses.
|
||||
|
@ -37,3 +37,5 @@ You can check and modify your issue subscription status under the “Notificatio
|
|||
When you watch a repository (by clicking on the “Watch” button in a repository), you will receive emails for every change (creation of issues, pull requests, comments, etc.) done in this repository.
|
||||
|
||||
To stop watching a repository, simply click on “Unwatch” in a repository.
|
||||
|
||||
To list all of your watched repositories, click on `/notifications/watching`. Alternatively you can click the menu button “Profile and Settings...” in the top-right corner of Forgejo and click on "Subscriptions" in the dropdown.
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
layout: '~/layouts/Markdown.astro'
|
||||
title: Your First Repository
|
||||
license: 'CC-BY-SA-4.0'
|
||||
origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/95574213ea1b57f207f60a12557ffbfc349ee274/content/getting-started/first-repository.md'
|
||||
origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/2887826c38b3aae76a18f0696b40217b429226ce/content/getting-started/first-repository.md'
|
||||
---
|
||||
|
||||
Almost everything on Forgejo happens in a repository. Think of a repository as a home for your project, where all of its source code can be organized using Git, as well as where you can track issues and read and write wikis.
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
layout: '~/layouts/Markdown.astro'
|
||||
title: 'The Basics of Issue Tracking'
|
||||
license: 'CC-BY-SA-4.0'
|
||||
origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/95574213ea1b57f207f60a12557ffbfc349ee274/content/getting-started/issue-tracking-basics.md'
|
||||
origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/2887826c38b3aae76a18f0696b40217b429226ce/content/getting-started/issue-tracking-basics.md'
|
||||
---
|
||||
|
||||
Issues are an important mean of communication on Forgejo.
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
layout: '~/layouts/Markdown.astro'
|
||||
title: 'Repository Permissions'
|
||||
license: 'CC-BY-SA-4.0'
|
||||
origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/95574213ea1b57f207f60a12557ffbfc349ee274/content/collaborating/repo-permissions.md'
|
||||
origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/2887826c38b3aae76a18f0696b40217b429226ce/content/collaborating/repo-permissions.md'
|
||||
---
|
||||
|
||||
<!-- See also https://github.com/go-gitea/gitea/blob/62ac3251fa545d32bdfc9ff824106b97ec63edbb/docs/content/doc/usage/permissions.en-us.md -->
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
layout: '~/layouts/Markdown.astro'
|
||||
title: 'Integrated Wiki'
|
||||
license: 'CC-BY-SA-4.0'
|
||||
origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/95574213ea1b57f207f60a12557ffbfc349ee274/content/getting-started/wiki.md'
|
||||
origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/2887826c38b3aae76a18f0696b40217b429226ce/content/getting-started/wiki.md'
|
||||
---
|
||||
|
||||
A [wiki](https://en.wikipedia.org/wiki/Wiki) is a collaborative space on the web. It is a common practice to use wikis to collect knowledge and share information.
|
||||
|
|
Loading…
Reference in a new issue