Octomerger Bot
@@ -59,9 +59,9 @@ jobs:
|
||||
language_dir: translations/fr-FR
|
||||
language_repo: github/docs-internal.fr-fr
|
||||
|
||||
# - language: de
|
||||
# language_dir: translations/de-DE
|
||||
# language_repo: github/docs-internal.de-de
|
||||
- language: de
|
||||
language_dir: translations/de-DE
|
||||
language_repo: github/docs-internal.de-de
|
||||
|
||||
steps:
|
||||
- name: Set branch name
|
||||
|
||||
@@ -36,7 +36,7 @@ jobs:
|
||||
fail-fast: false
|
||||
matrix:
|
||||
# This needs to match the languages we support
|
||||
language: [en, ja, es, pt, cn, ru, fr, ko]
|
||||
language: [en, ja, es, pt, cn, ru, fr, ko, de]
|
||||
steps:
|
||||
- if: ${{ env.FREEZE == 'true' }}
|
||||
run: |
|
||||
|
||||
BIN
assets/images/help/classroom/classroom-card.png
Normal file
BIN
assets/images/help/classroom/classroom-card.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 49 KiB |
BIN
assets/images/help/classroom/edit-assignment-add-test.png
Normal file
BIN
assets/images/help/classroom/edit-assignment-add-test.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 271 KiB |
BIN
assets/images/help/classroom/edit-assignment-admin-access.png
Normal file
BIN
assets/images/help/classroom/edit-assignment-admin-access.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 108 KiB |
BIN
assets/images/help/classroom/edit-assignment-deadline.png
Normal file
BIN
assets/images/help/classroom/edit-assignment-deadline.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 274 KiB |
BIN
assets/images/help/classroom/edit-assignment-edit-test.png
Normal file
BIN
assets/images/help/classroom/edit-assignment-edit-test.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 98 KiB |
BIN
assets/images/help/classroom/edit-assignment-feedback.png
Normal file
BIN
assets/images/help/classroom/edit-assignment-feedback.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 84 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 30 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 46 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 32 KiB |
BIN
assets/images/help/classroom/edit-assignment-status-dropdown.png
Normal file
BIN
assets/images/help/classroom/edit-assignment-status-dropdown.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 128 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 220 KiB |
BIN
assets/images/help/classroom/edit-assignment-title.png
Normal file
BIN
assets/images/help/classroom/edit-assignment-title.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 31 KiB |
BIN
assets/images/help/classroom/edit-assignment.png
Normal file
BIN
assets/images/help/classroom/edit-assignment.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 50 KiB |
@@ -74,6 +74,8 @@ If you've already created a group assignment for the classroom, you can reuse a
|
||||
|
||||
### Choosing a visibility for assignment repositories
|
||||
|
||||
{% data reusables.classroom.assignments-repository-visibility-and-permissions %}
|
||||
|
||||
{% data reusables.classroom.assignments-guide-choose-visibility %}
|
||||
|
||||
{% data reusables.classroom.assignments-guide-click-continue-after-basics %}
|
||||
|
||||
@@ -54,6 +54,8 @@ Under "Individual or group assignment", select the drop-down menu, and click **I
|
||||
|
||||
### Choosing a visibility for assignment repositories
|
||||
|
||||
{% data reusables.classroom.assignments-repository-visibility-and-permissions %}
|
||||
|
||||
{% data reusables.classroom.assignments-guide-choose-visibility %}
|
||||
|
||||
{% data reusables.classroom.assignments-guide-click-continue-after-basics %}
|
||||
|
||||
@@ -0,0 +1,117 @@
|
||||
---
|
||||
title: Editing an assignment
|
||||
intro: You can edit existing assignments in your course.
|
||||
versions:
|
||||
fpt: '*'
|
||||
permissions: 'Organization owners who are admins for a classroom can edit assignments for that classroom. {% data reusables.classroom.classroom-admins-link %}'
|
||||
shortTitle: Edit an assignment
|
||||
---
|
||||
## About editing assignments
|
||||
|
||||
After creating an assignment, you can edit many aspects of the assignment to better fit the needs of yourself and your students. Be aware that you cannot change the assignment type (either individual or group) or the online integrated development environment (IDE) after assignment creation. For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment)" and "[Create a group assignment](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment)."
|
||||
|
||||
## Editing an existing assignment
|
||||
|
||||
1. Sign into {% data variables.product.prodname_classroom_with_url %}.
|
||||
1. Navigate to a classroom.
|
||||
|
||||
|
||||
|
||||
1. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, next to the assignment you would like to edit, click {% octicon "pencil" aria-label="The pencil icon" %}.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You can also edit an assignment from the assignment's page. To access the assignment's page, in the **Assignments** tab, click the assignment name.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
|
||||
1. Under "Assignment title," click in the text field, then delete the existing text and type the new assignment title.
|
||||
|
||||
|
||||
|
||||
1. Optionally, to edit the default prefix for each student's assignment repository, click {% octicon "pencil" aria-label="The pencil icon" %}.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Editing an assignment's title or default repository prefix will not change the name of existing assignment repositories.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
|
||||
Then, type the new prefix under "Custom repository prefix."
|
||||
|
||||
|
||||
|
||||
1. Under "Deadline (optional)," click in the text field, then use the date picker to reassign a deadline. The new deadline cannot be in the past, and reassigning a deadline will update the deadline for all students.
|
||||
|
||||
|
||||
|
||||
1. To change the status of an assignment, select the **Assignment status** dropdown menu, then click **Active** or **Inactive**.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Inactive assignments cannot be accepted by students. You should change an assignment status to inactive once no more students should accept an assignment or the assignment deadline has passed.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
|
||||
1. Under "Repository visibility," select a visibility. If you use private repositories, only the student or team can see the feedback you provide.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Changing the visibility for assignment repositories will not retroactively change the visibility of existing assignment repositories.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
|
||||
1. Optionally, select or deselect **Grant students admin access to their repository**. For more information on admin permissions for repositories, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Granting or revoking student admin access after an assignment has been created will not retroactively change the permissions for existing assignment repositories.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
|
||||
1. To set up or change the template repository for your assignment, in the "Add a template repository to give students starter code" section, select the **Select a repository** dropdown menu.
|
||||
- To choose a template repository, begin typing the repository name in the text field, then click the repository in the search results.
|
||||
- To remove a template repository, delete any text in the text field.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** By default, an assignment will create an empty repository for each student on the roster for the classroom.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
|
||||
1. To add a new autograding test, in the "Add autograding tests" section, select the **Add test** drop-down menu, then click a grading method from the options that appear. For more information, see "[Use autograding](/education/manage-coursework-with-github-classroom/use-autograding)."
|
||||
|
||||
|
||||
|
||||
Additionally, you can edit or delete existing autograding tests with {% octicon "pencil" aria-label="The pencil icon" %} or {% octicon "trash" aria-label="The trash icon" %}.
|
||||
|
||||
|
||||
|
||||
1. To turn feedback pull requests on or off, select or deselect **Enable feedback pull requests**.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Enabling or disabling feedback pull requests for an assignment will not create or delete feedback pull requests for existing assignment repositories.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
|
||||
{% data reusables.classroom.update-assignment %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Create an individual assignment](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment)"
|
||||
- "[Create a group assignment](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment)"
|
||||
@@ -11,6 +11,7 @@ children:
|
||||
- /use-the-git-and-github-starter-assignment
|
||||
- /create-an-individual-assignment
|
||||
- /create-a-group-assignment
|
||||
- /editing-an-assignment
|
||||
- /reuse-an-assignment
|
||||
- /create-an-assignment-from-a-template-repository
|
||||
- /leave-feedback-with-pull-requests
|
||||
|
||||
@@ -1,7 +1,3 @@
|
||||
The repositories for an assignment can be public or private. If you use private repositories, only the student or team can see the feedback you provide.
|
||||
|
||||
You can also decide whether to grant students admin permissions to the repository for an assignment. Grant admin permissions if the student should be able to perform administrative tasks for the assignment repository. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
|
||||
|
||||
Under "Repository visibility", select a visibility. Optionally, select **Grant students admin access to their repository**.
|
||||
|
||||
<div class="procedural-image-wrapper">
|
||||
|
||||
@@ -0,0 +1,3 @@
|
||||
The repositories for an assignment can be public or private. If you use private repositories, only the student or team can see the feedback you provide.
|
||||
|
||||
You can also decide whether to grant students admin permissions to the repository for an assignment. Grant admin permissions if the student should be able to perform administrative tasks for the assignment repository. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
|
||||
2
data/reusables/classroom/update-assignment.md
Normal file
2
data/reusables/classroom/update-assignment.md
Normal file
@@ -0,0 +1,2 @@
|
||||
1. Click **Update assignment**.
|
||||
|
||||
@@ -11,6 +11,7 @@ const possibleEnvVars = {
|
||||
'zh-CN': process.env.TRANSLATIONS_ROOT_ZH_CN,
|
||||
'ja-JP': process.env.TRANSLATIONS_ROOT_JA_JP,
|
||||
'pt-BR': process.env.TRANSLATIONS_ROOT_PT_BR,
|
||||
'de-DE': process.env.TRANSLATIONS_ROOT_DE_DE,
|
||||
'fr-FR': process.env.TRANSLATIONS_ROOT_FR_FR,
|
||||
'ru-RU': process.env.TRANSLATIONS_ROOT_RU_RU,
|
||||
'ko-KR': process.env.TRANSLATIONS_ROOT_KO_KR,
|
||||
@@ -72,6 +73,14 @@ const languages = {
|
||||
dir: getRoot('pt-BR'),
|
||||
wip: false,
|
||||
},
|
||||
de: {
|
||||
name: 'German',
|
||||
nativeName: 'Deutsch',
|
||||
code: 'de',
|
||||
hreflang: 'de',
|
||||
dir: getRoot('de-DE'),
|
||||
wip: true,
|
||||
},
|
||||
fr: {
|
||||
name: 'French',
|
||||
nativeName: 'Français',
|
||||
@@ -90,7 +99,7 @@ const languages = {
|
||||
},
|
||||
ko: {
|
||||
name: 'Korean',
|
||||
nativeName: 'Korean',
|
||||
nativeName: '한국어',
|
||||
code: 'ko',
|
||||
hreflang: 'ko',
|
||||
dir: getRoot('ko-KR'),
|
||||
|
||||
@@ -26,6 +26,6 @@ export default {
|
||||
return
|
||||
}
|
||||
|
||||
return this.liquid.parseAndRender(text, scope.environments)
|
||||
return this.liquid.parseAndRender(text.trim(), scope.environments)
|
||||
},
|
||||
}
|
||||
|
||||
1
translations/de-DE/Placeholder.txt
Normal file
1
translations/de-DE/Placeholder.txt
Normal file
@@ -0,0 +1 @@
|
||||
Placeholder
|
||||
50
translations/de-DE/content/account-and-profile/index.md
Normal file
50
translations/de-DE/content/account-and-profile/index.md
Normal file
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: Dein Konto und Profil auf GitHub
|
||||
shortTitle: Account and profile
|
||||
intro: 'Stelle sicher, dass {% data variables.product.product_name %} optimal für dich funktioniert, indem du die Einstellungen für dein persönliches Konto anpasst, deine Profilseite personalisierst und die Benachrichtigungen verwaltest, die du für Aktivitäten auf {% data variables.product.prodname_dotcom %} erhältst.'
|
||||
introLinks:
|
||||
quickstart: /get-started/onboarding/getting-started-with-your-github-account
|
||||
featuredLinks:
|
||||
guides:
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username
|
||||
- '{% ifversion ghae %}/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard{% endif %}'
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme
|
||||
- '{% ifversion ghae %}/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile{% endif %}'
|
||||
- /account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications
|
||||
popular:
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository
|
||||
- /account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications
|
||||
guideCards:
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile
|
||||
- /account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address
|
||||
- '{% ifversion ghes or ghae %}/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories{% endif %}'
|
||||
changelog:
|
||||
label: 'profiles, github-themes, notifications'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
layout: product-landing
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
- Profiles
|
||||
- Notifications
|
||||
children:
|
||||
- /setting-up-and-managing-your-personal-account-on-github
|
||||
- /setting-up-and-managing-your-github-profile
|
||||
- /managing-subscriptions-and-notifications-on-github
|
||||
ms.openlocfilehash: 922990e3a89a53f625e739650c3c3b329f1f497d
|
||||
ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/12/2022
|
||||
ms.locfileid: '147888460'
|
||||
---
|
||||
|
||||
@@ -0,0 +1,28 @@
|
||||
---
|
||||
title: Abonnements und Benachrichtigungen auf GitHub verwalten
|
||||
intro: 'Du kannst angeben, wie du Benachrichtigungen erhalten möchtest, für welche Repositorys du dich interessierst und über welche Arten von Aktivitäten du informiert werden möchtest.'
|
||||
redirect_from:
|
||||
- /categories/76/articles
|
||||
- /categories/notifications
|
||||
- /categories/receiving-notifications-about-activity-on-github
|
||||
- /github/managing-subscriptions-and-notifications-on-github
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Notifications
|
||||
children:
|
||||
- /setting-up-notifications
|
||||
- /viewing-and-triaging-notifications
|
||||
- /managing-subscriptions-for-activity-on-github
|
||||
shortTitle: Subscriptions & notifications
|
||||
ms.openlocfilehash: 33c5c21db5feb48ca234e2ba45173f480fb53f8f
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145103112'
|
||||
---
|
||||
|
||||
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: Verwaltung von Abonnements für Aktivitäten auf GitHub
|
||||
intro: 'Um nachhaltige Workflows für Benachrichtigungen zu unterhalten, verstehe und überprüfe regelmäßig Deine Abonnements.'
|
||||
redirect_from:
|
||||
- /github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Notifications
|
||||
children:
|
||||
- /viewing-your-subscriptions
|
||||
- /managing-your-subscriptions
|
||||
shortTitle: Manage subscriptions
|
||||
ms.openlocfilehash: e1457283f0027dd2b668d6096e2f04273e920a71
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145086063'
|
||||
---
|
||||
|
||||
@@ -0,0 +1,84 @@
|
||||
---
|
||||
title: Managing your subscriptions
|
||||
intro: 'To help you manage your notifications efficiently, there are several ways to unsubscribe.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Notifications
|
||||
redirect_from:
|
||||
- /github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions
|
||||
- /github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions
|
||||
shortTitle: Manage your subscriptions
|
||||
---
|
||||
To help you understand your subscriptions and decide whether to unsubscribe, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Instead of unsubscribing, you have the option to ignore a repository. If you ignore a repository, you won't receive any notifications. We don't recommend ignoring repositories as you won't be notified if you're @mentioned. {% ifversion fpt or ghec %}If you're experiencing abuse and want to ignore a repository, please contact {% data variables.contact.contact_support %} so we can help. {% data reusables.policies.abuse %}{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Choosing how to unsubscribe
|
||||
|
||||
To unwatch (or unsubscribe from) repositories quickly, navigate to [github.com/watching](https://github.com/watching) to see all the repositories you're following. For more information, see "[Unwatching repositories](#unwatching-repositories)."
|
||||
|
||||
To unsubscribe from multiple notifications at the same time, you can unsubscribe using your inbox or on the subscriptions page. Both of these options offer more context about your subscriptions than the "Watched repositories" page.
|
||||
|
||||
### Benefits of unsubscribing from your inbox
|
||||
|
||||
When you unsubscribe from notifications in your inbox, you have several other triaging options and can filter your notifications by custom filters and discussion types. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)."
|
||||
|
||||
### Benefits of unsubscribing from the subscriptions page
|
||||
|
||||
When you unsubscribe from notifications on the subscriptions page, you can see more of the notifications you're subscribed to and sort them by "Most recently subscribed" or "Least recently subscribed".
|
||||
|
||||
The subscriptions page shows you all of the notifications that you're currently subscribed to, including notifications that you have marked as **Done** in your inbox.
|
||||
|
||||
You can only filter your subscriptions by repository and the reason you're receiving the notification.
|
||||
|
||||
## Unsubscribing from notifications in your inbox
|
||||
|
||||
When you unsubscribe from notifications in your inbox, they will automatically disappear from your inbox.
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
1. From the notifications inbox, select the notifications you want to unsubscribe to.
|
||||
2. Click **Unsubscribe.**
|
||||
|
||||
|
||||
## Unsubscribing from notifications on the subscriptions page
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down to click **Subscriptions**.
|
||||
|
||||
|
||||
2. Select the notifications you want to unsubscribe to. In the top right, click **Unsubscribe.**
|
||||
|
||||
|
||||
## Unwatching repositories
|
||||
|
||||
When you unwatch a repository, you unsubscribe from future updates from that repository unless you participate in a conversation or are @mentioned.
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down to click **Watched repositories**.
|
||||
|
||||
|
||||
|
||||
2. On the watched repositories page, after you've evaluated the repositories you're watching, choose whether to:
|
||||
|
||||
- Unwatch a repository
|
||||
- Ignore all notifications for a repository
|
||||
- If enabled, customize the types of event you receive notifications for ({% data reusables.notifications-v2.custom-notification-types %})
|
||||
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
|
||||
1. Optionally, to unsubscribe from all repositories owned by a given user or organization, select the **Unwatch all** dropdown and click the organization whose repositories you'd like to unsubscribe from. The button to unwatch all repositories is only available if you are watching all activity or custom notifications on over 10 repositories.
|
||||
|
||||
|
||||
|
||||
- Click **Unwatch** to confirm that you want to unwatch the repositories owned by the selected user or organization, or click **Cancel** to cancel.
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
@@ -0,0 +1,84 @@
|
||||
---
|
||||
title: Viewing your subscriptions
|
||||
intro: 'To understand where your notifications are coming from and your notifications volume, we recommend reviewing your subscriptions and watched repositories regularly.'
|
||||
redirect_from:
|
||||
- /articles/subscribing-to-conversations
|
||||
- /articles/unsubscribing-from-conversations
|
||||
- /articles/subscribing-to-and-unsubscribing-from-notifications
|
||||
- /articles/listing-the-issues-and-pull-requests-youre-subscribed-to
|
||||
- /articles/watching-repositories
|
||||
- /articles/unwatching-repositories
|
||||
- /articles/watching-and-unwatching-repositories
|
||||
- /articles/watching-and-unwatching-releases-for-a-repository
|
||||
- /articles/watching-and-unwatching-team-discussions
|
||||
- /articles/listing-watched-repositories
|
||||
- /articles/listing-the-repositories-you-re-watching
|
||||
- /articles/listing-the-repositories-youre-watching
|
||||
- /github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions
|
||||
- /github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Notifications
|
||||
shortTitle: View subscriptions
|
||||
---
|
||||
You receive notifications for your subscriptions of ongoing activity on {% data variables.product.product_name %}. There are many reasons you can be subscribed to a conversation. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)."
|
||||
|
||||
We recommend auditing and unsubscribing from your subscriptions as a part of a healthy notifications workflow. For more information about your options for unsubscribing, see "[Managing subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
|
||||
|
||||
## Diagnosing why you receive too many notifications
|
||||
|
||||
When your inbox has too many notifications to manage, consider whether you have oversubscribed or how you can change your notification settings to reduce the subscriptions you have and the types of notifications you're receiving. For example, you may consider disabling the settings to automatically watch all repositories and all team discussions whenever you've joined a team or repository.
|
||||
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
|
||||
{% else %}
|
||||
{% endif %}
|
||||
|
||||
For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)."
|
||||
|
||||
To see an overview of your repository subscriptions, see "[Reviewing repositories that you're watching](#reviewing-repositories-that-youre-watching)."
|
||||
{% tip %}
|
||||
|
||||
**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.product_name %}. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
Many people forget about repositories that they've chosen to watch in the past. From the "Watched repositories" page you can quickly unwatch repositories. For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage workflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)."
|
||||
|
||||
## Reviewing all of your subscriptions
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
1. In the left sidebar, under the list of repositories that you have notifications from, use the "Manage notifications" drop-down to click **Subscriptions**.
|
||||
|
||||
|
||||
2. Use the filters and sort to narrow the list of subscriptions and begin unsubscribing to conversations you no longer want to receive notifications for.
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tips:**
|
||||
- To review subscriptions you may have forgotten about, sort by "least recently subscribed."
|
||||
|
||||
- To review a list of repositories that you can still receive notifications for, see the repository list in the "filter by repository" drop-down menu.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## Reviewing repositories that you're watching
|
||||
|
||||
1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down menu and click **Watched repositories**.
|
||||
|
||||
2. Evaluate the repositories that you are watching and decide if their updates are still relevant and helpful. When you watch a repository, you will be notified of all conversations for that repository.
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** Instead of watching a repository, consider only receiving notifications when there are updates to {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository), or any combination of these options, or completely unwatching a repository.
|
||||
|
||||
When you unwatch a repository, you can still be notified when you're @mentioned or participating in a thread. When you configure to receive notifications for certain event types, you're only notified when there are updates to these event types in the repository, you're participating in a thread, or you or a team you're on is @mentioned.
|
||||
|
||||
{% endtip %}
|
||||
@@ -0,0 +1,99 @@
|
||||
---
|
||||
title: About notifications
|
||||
intro: 'Notifications provide updates about the activity on {% data variables.location.product_location %} that you''ve subscribed to. You can use the notifications inbox to customize, triage, and manage your updates.'
|
||||
redirect_from:
|
||||
- /articles/notifications
|
||||
- /articles/about-notifications
|
||||
- /github/managing-subscriptions-and-notifications-on-github/about-notifications-beta
|
||||
- /github/managing-subscriptions-and-notifications-on-github/about-notifications
|
||||
- /github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Notifications
|
||||
---
|
||||
|
||||
## Notifications and subscriptions
|
||||
|
||||
You can choose to receive ongoing updates about specific activity on {% data variables.location.product_location %} through a subscription. Notifications are updates that you receive for specific activity that you are subscribed to.
|
||||
|
||||
### Subscription options
|
||||
|
||||
You can choose to subscribe to notifications for:
|
||||
- A conversation in a specific issue, pull request, or gist.
|
||||
- All activity in a repository or team discussion.
|
||||
- CI activity, such as the status of workflows in repositories set up with {% data variables.product.prodname_actions %}.
|
||||
- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled).
|
||||
|
||||
You can also choose to automatically watch all repositories that you have push access to, except forks. You can watch any other repository you have access to manually by clicking **Watch**.
|
||||
|
||||
If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For example, if you no longer want to receive notifications from a particular repository, you can click **Unsubscribe**. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
|
||||
|
||||
### Default subscriptions
|
||||
|
||||
In general, you are automatically subscribed to conversations by default when you have:
|
||||
- Not disabled automatic watching for repositories or teams you've joined in your notification settings. This setting is enabled by default.
|
||||
- Been assigned to an issue or pull request.
|
||||
- Opened a pull request, issue, or created a team discussion post.
|
||||
- Commented on a thread.
|
||||
- Subscribed to a thread manually by clicking **Watch** or **Subscribe**.
|
||||
- Had your username @mentioned.
|
||||
- Changed the state of a thread, such as by closing an issue or merging a pull request.
|
||||
- Had a team you're a member of @mentioned.
|
||||
|
||||
By default, you also automatically watch all repositories that you create and are owned by your personal account.
|
||||
|
||||
To unsubscribe from conversations you're automatically subscribed to, you can change your notification settings or directly unsubscribe or unwatch activity on {% data variables.location.product_location %}. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
|
||||
|
||||
## Customizing notifications and subscriptions
|
||||
|
||||
You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% ifversion fpt or ghes or ghec %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options.
|
||||
|
||||
To customize the types of updates you'd like to receive and where to send those updates, configure your notification settings. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)."
|
||||
|
||||
To keep your subscriptions manageable, review your subscriptions and watched repositories and unsubscribe as needed. For more information, see "[Managing subscriptions for activity on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)."
|
||||
|
||||
To customize how you'd like to receive updates for specific pull requests or issues, you can configure your preferences within the issue or pull request. For more information, see "[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)."
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
You can customize and schedule push notifications in the {% data variables.product.prodname_mobile %} app. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#managing-your-notification-settings-with-github-mobile)."
|
||||
{% endif %}
|
||||
|
||||
## Reasons for receiving notifications
|
||||
|
||||
Your inbox is configured with default filters, which represent the most common reasons that people need to follow-up on their notifications. For more information about inbox filters, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#default-notification-filters)."
|
||||
|
||||
Your inbox shows the `reasons` you're receiving notifications as a label.
|
||||
|
||||
|
||||
|
||||
You can filter your inbox by the reason you're subscribed to notifications. For example, to only see pull requests where someone requested your review, you can use the `review-requested` query filter.
|
||||
|
||||
|
||||
|
||||
If you've configured notifications to be sent by email and believe you're receiving notifications that don't belong to you, consider troubleshooting with email headers, which show the intended recipient. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)."
|
||||
|
||||
## Triaging notifications from your inbox
|
||||
|
||||
To effectively manage your notifications, you can triage your inbox with options to:
|
||||
- Remove a notification from the inbox with **Done**. You can review **Done** notifications all in one place by clicking **Done** in the sidebar or by using the query `is:done`.
|
||||
- Mark a notification as read or unread.
|
||||
- **Save** a notification for later review. **Saved** notifications are flagged in your inbox. You can review **Saved** notifications all in one place in the sidebar by clicking **Saved** or by using the query `is:saved`.
|
||||
- Automatically unsubscribe from this notification and future updates from this conversation. Unsubscribing also removes the notification from your inbox. If you unsubscribe from a conversation and someone mentions your username or a team you're on that you're receiving updates for, then you will start to receive notifications from this conversation again.
|
||||
|
||||
From your inbox you can also triage multiple notifications at once. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)."
|
||||
|
||||
## Customizing your notifications inbox
|
||||
|
||||
To focus on a group of notifications in your inbox on {% data variables.location.product_location %}{% ifversion fpt or ghes or ghec %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. For example, you can create a custom filter for an open source project you contribute to and only see notifications for that repository in which you are mentioned. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)." For more examples of how to customize your triaging workflow, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)."
|
||||
|
||||
## Notification retention policy
|
||||
|
||||
Notifications that are not marked as **Saved** are kept for 5 months. Notifications marked as **Saved** are kept indefinitely. If your saved notification is older than 5 months and you unsave it, the notification will disappear from your inbox within a day.
|
||||
|
||||
## Feedback and support
|
||||
|
||||
If you have feedback or feature requests for notifications, use a [{% data variables.product.prodname_github_community %} discussion](https://github.com/orgs/community/discussions/categories/general).
|
||||
@@ -0,0 +1,304 @@
|
||||
---
|
||||
title: Configuring notifications
|
||||
intro: 'Choose the type of activity on {% data variables.product.prodname_dotcom %} that you want to receive notifications for and how you want these updates delivered.'
|
||||
redirect_from:
|
||||
- /articles/about-web-notifications
|
||||
- /format-of-notification-emails
|
||||
- /articles/configuring-notification-emails
|
||||
- /articles/about-notification-emails
|
||||
- /articles/about-email-notifications
|
||||
- /articles/accessing-your-notifications
|
||||
- /articles/configuring-notification-delivery-methods
|
||||
- /articles/managing-notification-delivery-methods
|
||||
- /articles/managing-notification-emails-for-organizations
|
||||
- /articles/choosing-the-delivery-method-for-your-notifications
|
||||
- /articles/choosing-the-types-of-notifications-you-receive
|
||||
- /github/managing-subscriptions-and-notifications-on-github/configuring-notifications
|
||||
- /github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Notifications
|
||||
---
|
||||
|
||||
## Notification delivery options
|
||||
|
||||
You can receive notifications for activity on {% data variables.location.product_location %} in the following locations.
|
||||
|
||||
- The notifications inbox in the {% data variables.location.product_location %} web interface{% ifversion fpt or ghes or ghec %}
|
||||
- The notifications inbox on {% data variables.product.prodname_mobile %}, which syncs with the inbox on {% data variables.location.product_location %}{% endif %}
|
||||
- An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.location.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
{% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Choosing your notification settings](#choosing-your-notification-settings)."
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.notifications.shared_state %}
|
||||
|
||||
### Benefits of the notifications inbox
|
||||
|
||||
The notifications inbox on {% data variables.location.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.prodname_dotcom %} notifications flow, including options to:
|
||||
- Triage multiple notifications at once.
|
||||
- Mark completed notifications as **Done** and remove them from your inbox. To view all of your notifications marked as **Done**, use the `is:done` query.
|
||||
- Save a notification to review later. Saved notifications are flagged in your inbox and kept indefinitely. To view all of your saved notifications, use the `is:saved` query.
|
||||
- Unsubscribe and remove a notification from your inbox.
|
||||
- Preview the issue, pull request, or team discussion where the notification originates on {% data variables.location.product_location %} from within the notifications inbox.
|
||||
- See one of the latest reasons you're receiving a notification from your inbox with a `reasons` label.
|
||||
- Create custom filters to focus on different notifications when you want.
|
||||
- Group notifications in your inbox by repository or date to get a quick overview with less context switching
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
In addition, you can receive and triage notifications on your mobile device with {% data variables.product.prodname_mobile %}. For more information, see "[Managing your notification settings with GitHub Mobile](#managing-your-notification-settings-with-github-mobile)" or "[GitHub Mobile](/get-started/using-github/github-mobile)."
|
||||
{% endif %}
|
||||
|
||||
### Benefits of using an email client for notifications
|
||||
|
||||
One benefit of using an email client is that all of your notifications can be kept indefinitely depending on your email client's storage capacity. Your inbox notifications are only kept for 5 months on {% data variables.product.prodname_dotcom %} unless you've marked them as **Saved**. **Saved** notifications are kept indefinitely. For more information about your inbox's retention policy, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)."
|
||||
|
||||
Sending notifications to your email client also allows you to customize your inbox according to your email client's settings, which can include custom or color-coded labels.
|
||||
|
||||
Email notifications also allow flexibility with the types of notifications you receive and allow you to choose different email addresses for updates. For example, you can send certain notifications for a repository to a verified personal email address. For more information, about your email customization options, see "[Customizing your email notifications](#customizing-your-email-notifications)."
|
||||
|
||||
## About participating and watching notifications
|
||||
|
||||
When you watch a repository, you're subscribing to updates for activity in that repository. Similarly, when you watch a specific team's discussions, you're subscribing to all conversation updates on that team's page. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
|
||||
|
||||
To see repositories that you're watching, go to your [watching page](https://github.com/watching). For more information, see "[Managing subscriptions and notifications on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)."
|
||||
|
||||
{% ifversion ghae %}
|
||||
### Configuring notifications
|
||||
{% endif %}
|
||||
You can configure notifications for a repository on the repository page, or on your watching page.
|
||||
|
||||
### About custom notifications
|
||||
You can customize notifications for a repository. For example, you can choose to only be notified when updates to one or more types of events ({% data reusables.notifications-v2.custom-notification-types %}) happen within a repository, or ignore all notifications for a repository. For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below.
|
||||
|
||||
### Participating in conversations
|
||||
Anytime you comment in a conversation or when someone @mentions your username, you are _participating_ in a conversation. By default, you are automatically subscribed to a conversation when you participate in it. You can unsubscribe from a conversation you've participated in manually by clicking **Unsubscribe** on the issue or pull request or through the **Unsubscribe** option in the notifications inbox.
|
||||
|
||||
{% ifversion update-notification-settings-22 %}For conversations you're watching or participating in, you can choose whether you want to receive notifications on {% data variables.product.company_short %} or by email in your notification settings. For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.location.product_location %}{% ifversion ghes %} and {% data variables.product.prodname_mobile %}{% endif %}. For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
|
||||
For example:
|
||||
- If you don't want notifications to be sent to your email, unselect **email** for participating and watching notifications.
|
||||
- If you want to receive notifications by email when you've participated in a conversation, then you can select **email** under "Participating".
|
||||
|
||||
{% ifversion update-notification-settings-22 %}If you do not enable "Notify me: On GitHub" for watching or participating notifications, then your notifications inbox will not have any updates.
|
||||
|
||||
{% else %}
|
||||
|
||||
If you do not enable watching or participating notifications for web{% ifversion ghes %} and mobile{% endif %}, then your notifications inbox will not have any updates.{% endif %}
|
||||
|
||||
## Customizing your email notifications
|
||||
|
||||
After enabling email notifications, {% data variables.location.product_location %} will send notifications to you as multipart emails that contain both HTML and plain text copies of the content. Email notification content includes any Markdown, @mentions, emojis, hash-links, and more, that appear in the original content on {% data variables.location.product_location %}. If you only want to see the text in the email, you can configure your email client to display the plain text copy only.
|
||||
|
||||
{% data reusables.notifications.outbound_email_tip %}
|
||||
|
||||
{% data reusables.notifications.shared_state %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
If you're using Gmail, you can click a button beside the notification email to visit the original issue or pull request that generated the notification.
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
Choose a default email address where you want to send updates for conversations you're participating in or watching. You can also specify which activity on {% data variables.location.product_location %} you want to receive updates for using your default email address. For example, choose whether you want updates to your default email from:
|
||||
- Comments on issues and pull requests.
|
||||
- Pull request reviews.
|
||||
- Pull request pushes.
|
||||
- Your own updates, such as when you open, comment on, or close an issue or pull request.
|
||||
|
||||
Depending on the organization that owns the repository, you can also send notifications to different email addresses. Your organization may require the email address to be verified for a specific domain. For more information, see "[Choosing where your organization’s email notifications are sent](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-where-your-organizations-email-notifications-are-sent)."
|
||||
|
||||
You can also send notifications for a specific repository to an email address. For more information, see "[About email notifications for pushes to your repository](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)."
|
||||
|
||||
{% data reusables.notifications-v2.email-notification-caveats %}
|
||||
|
||||
## Filtering email notifications
|
||||
|
||||
Each email notification that {% data variables.location.product_location %} sends contains header information. The header information in every email is consistent, so you can use it in your email client to filter or forward all {% data variables.product.prodname_dotcom %} notifications, or certain types of {% data variables.product.prodname_dotcom %} notifications.
|
||||
|
||||
If you believe you're receiving notifications that don't belong to you, examine the `X-GitHub-Recipient` and `X-GitHub-Recipient-Address` headers. These headers show who the intended recipient is. Depending on your email setup, you may receive notifications intended for another user.
|
||||
|
||||
Email notifications from {% data variables.location.product_location %} contain the following header information:
|
||||
|
||||
| Header | Information |
|
||||
| --- | --- |
|
||||
| `From` address | This address will always be {% ifversion fpt or ghec %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. |
|
||||
| `To` field | This field connects directly to the thread.{% ifversion not ghae %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} |
|
||||
| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are: <ul><li>`assign`: You were assigned to an issue or pull request.</li><li>`author`: You created an issue or pull request.</li><li>`ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.</li><li>`comment`: You commented on an issue or pull request.</li><li>`manual`: There was an update to an issue or pull request you manually subscribed to.</li><li>`mention`: You were mentioned on an issue or pull request.</li><li>`push`: Someone committed to a pull request you're subscribed to.</li><li>`review_requested`: You or a team you're a member of was requested to review a pull request.</li><li>`security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.</li><li>`state_change`: An issue or pull request you're subscribed to was either closed or opened.</li><li>`subscribed`: There was an update in a repository you're watching.</li><li>`team_mention`: A team you belong to was mentioned on an issue or pull request.</li><li>`your_activity`: You opened, commented on, or closed an issue or pull request.</li></ul> |
|
||||
| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `<repository name>.<repository owner>.{% data variables.command_line.backticks %}`. |
|
||||
| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:<ul><li>`low`</li><li>`moderate`</li><li>`high`</li><li>`critical`</li></ul>For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |
|
||||
|
||||
## Choosing your notification settings
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
{% data reusables.notifications-v2.manage-notifications %}
|
||||
3. On the notifications settings page, choose how you receive notifications when:
|
||||
- There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "[About participating and watching notifications](#about-participating-and-watching-notifications)."
|
||||
- You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."
|
||||
- There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} notification options](#dependabot-alerts-notification-options)." {% ifversion fpt or ghec %}
|
||||
- There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)."{% endif %}{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
|
||||
- There are new deploy keys added to repositories that belong to organizations that you're an owner of. For more information, see "[Organization alerts notification options](#organization-alerts-notification-options)."{% endif %}
|
||||
|
||||
## Automatic watching
|
||||
|
||||
By default, anytime you gain access to a new repository, you will automatically begin watching that repository. Anytime you join a new team, you will automatically be subscribed to updates and receive notifications when that team is @mentioned. If you don't want to automatically be subscribed, you can unselect the automatic watching options in your notification settings.
|
||||
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
|
||||
{% else %}
|
||||
{% endif %}
|
||||
|
||||
If "Automatically watch repositories" is disabled, then you will not automatically watch your own repositories. You must navigate to your repository page and choose the watch option.
|
||||
|
||||
For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
|
||||
|
||||
## Configuring your watch settings for an individual repository
|
||||
|
||||
You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository) , or completely ignore an individual repository.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
2. In the upper-right corner, select the "Watch" drop-down menu to click a watch option.
|
||||
|
||||
|
||||
The **Custom** option allows you to further customize notifications so that you're only notified when specific events happen in the repository, in addition to participating and @mentions.
|
||||
|
||||
If you select "Issues", you will be notified about, and subscribed to, updates on every issue (including those that existed prior to you selecting this option) in the repository. If you're @mentioned in a pull request in this repository, you'll receive notifications for that too, and you'll be subscribed to updates on that specific pull request, in addition to being notified about issues.
|
||||
|
||||
## Choosing where your organization’s email notifications are sent
|
||||
|
||||
If you belong to an organization, you can choose the email account you want notifications for organization activity sent to. For example, if you belong to an organization for work, you may want your notifications sent to your work email address, rather than your personal address.
|
||||
|
||||
{% data reusables.notifications-v2.email-notification-caveats %}
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
{% data reusables.notifications-v2.manage-notifications %}
|
||||
|
||||
3. Under "Default notification email", select the email address you'd like notifications sent to.
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghes or ghae %}
|
||||
4. Click **Save**.{% endif %}
|
||||
|
||||
### Customizing email routes per organization
|
||||
|
||||
If you are a member of more than one organization, you can configure each one to send notifications to any of{% ifversion fpt or ghec %} your verified email addresses{% else %} the email addresses for your account{% endif %}. {% ifversion fpt or ghec %} For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."{% endif %}
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
{% data reusables.notifications-v2.manage-notifications %}
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
3. Under "Default notifications email", click **Custom routing**.
|
||||
|
||||
|
||||
|
||||
4. Click **Add new route**.
|
||||
|
||||
|
||||
|
||||
5. Click **Pick organization**, then select the organization you want to customize from the dropdown.
|
||||
|
||||
|
||||
|
||||
6. Select one of your verified email addresses, then click **Save**.
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
3. Under "Custom routing," find your organization's name in the list.
|
||||
|
||||
|
||||
|
||||
4. Click **Edit** next to the email address you want to change.
|
||||
|
||||
|
||||
|
||||
5. Select one of your verified email addresses, then click **Save**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## {% data variables.product.prodname_dependabot_alerts %} notification options
|
||||
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-enable %}
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %}
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-options %}
|
||||
|
||||
For more information about the notification delivery methods available to you, and advice on optimizing your notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
|
||||
|
||||
{% ifversion update-notification-settings-22 or ghes %}
|
||||
## {% data variables.product.prodname_actions %} notification options
|
||||
|
||||
Choose how you want to receive workflow run updates for repositories that you are watching that are set up with {% data variables.product.prodname_actions %}. You can also choose to only receive notifications for failed workflow runs.{% endif %}
|
||||
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
{% endif %}
|
||||
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
|
||||
## Organization alerts notification options
|
||||
|
||||
If you're an organization owner, you'll receive email notifications by default when organization members add new deploy keys to repositories within the organization. You can unsubscribe from these notifications. On the notification settings page, under "Organization alerts", unselect **Email**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
## Managing your notification settings with {% data variables.product.prodname_mobile %}
|
||||
|
||||
When you install {% data variables.product.prodname_mobile %}, you will automatically be opted into web notifications. Within the app, you can enable push notifications for the following events.
|
||||
- Direct mentions
|
||||
- Assignments to issues or pull requests
|
||||
- Requests to review a pull request
|
||||
- Requests to approve a deployment
|
||||
|
||||
You can also schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device.
|
||||
|
||||
{% data reusables.mobile.push-notifications-on-ghes %}
|
||||
|
||||
### Managing your notification settings with {% data variables.product.prodname_ios %}
|
||||
|
||||
1. In the bottom menu, tap **Profile**.
|
||||
2. To view your settings, tap {% octicon "gear" aria-label="The Gear icon" %}.
|
||||
3. To update your notification settings, tap **Notifications** and then use the toggles to enable or disable your preferred types of push notifications.
|
||||
4. Optionally, to schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device, tap **Working Hours**, use the **Custom working hours** toggle, and then choose when you would like to receive push notifications.
|
||||
|
||||
### Managing your notification settings with {% data variables.product.prodname_android %}
|
||||
|
||||
1. In the bottom menu, tap **Profile**.
|
||||
2. To view your settings, tap {% octicon "gear" aria-label="The Gear icon" %}.
|
||||
3. To update your notification settings, tap **Configure Notifications** and then use the toggles to enable or disable your preferred types of push notifications.
|
||||
4. Optionally, to schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device, tap **Working Hours**, use the **Custom working hours** toggle, and then choose when you would like to receive push notifications.
|
||||
|
||||
## Configuring your watch settings for an individual repository with {% data variables.product.prodname_mobile %}
|
||||
|
||||
You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% ifversion fpt or ghec %}certain event types such as issues, pull requests, discussions (if enabled for the repository) and {% endif %}new releases, or completely ignore an individual repository.
|
||||
|
||||
1. On {% data variables.product.prodname_mobile %}, navigate to the main page of the repository.
|
||||
2. Tap **Watch**.
|
||||
|
||||
3. To choose what activities you receive notifications for, tap your preferred watch settings.
|
||||
|
||||
|
||||
{% endif %}
|
||||
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: Benachrichtigungen einrichten
|
||||
intro: 'Um die Relevanz Deiner Benachrichtigungen zu verbessern und den Selektions-Workflow zu vereinfachen, richte Deine Benachrichtigungen entsprechend Deinen Prioritäten ein.'
|
||||
redirect_from:
|
||||
- /articles/getting-started-with-notifications
|
||||
- /github/managing-subscriptions-and-notifications-on-github/setting-up-notifications
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Notifications
|
||||
children:
|
||||
- /about-notifications
|
||||
- /configuring-notifications
|
||||
ms.openlocfilehash: 7e2b668bbd02e5b9d0307559dca82dda5ae70ee8
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145104560'
|
||||
---
|
||||
|
||||
@@ -0,0 +1,78 @@
|
||||
---
|
||||
title: Anpassen eines Workflows zum Selektieren deiner Benachrichtigungen
|
||||
intro: 'Um einen idealen Workflow für das Selektieren deiner Benachrichtigungen zu erstellen, kannst du diese Beispielworkflows übernehmen und anpassen.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Notifications
|
||||
redirect_from:
|
||||
- /github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications
|
||||
- /github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/customizing-a-workflow-for-triaging-your-notifications
|
||||
shortTitle: Triage your notifications
|
||||
ms.openlocfilehash: 9e5771dff52408a1b6967a3792eb36eefebefd72
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145104559'
|
||||
---
|
||||
## Beginne deine Posteingang-Selektion
|
||||
|
||||
Bevor du mit der Selektion in deinem Posteingang beginnst, überlege Dir, ob du zuerst die wichtigsten Aktualisierungen finden und beantworten möchtest, oder ob du zuerst deinen Posteingang von störenden Benachrichtigungen leeren möchtest, die einfach zu finden und zu entfernen sind.
|
||||
|
||||
Ja nach Anzahl deiner Benachrichtigungen kannst du zu verschiedenen Zeiten auch eine Kombination der beiden Ansätze wählen.
|
||||
|
||||
Ein Beispiel für den Workflow zum Suchen und Reagieren auf die wichtigsten Benachrichtigungen findest du unter [Überprüfen der Benachrichtigungen mit den höchsten Prioritäten](#checking-your-highest-notification-priorities).
|
||||
|
||||
Ein Beispiel für den Workflow zum Entfernen von Benachrichtigungen, die einfach entfernt oder selektiert werden können, findest du unter [Löschen der am wenigsten wichtigen Benachrichtigungen](#clearing-your-least-important-notifications).
|
||||
|
||||
## Deine Benachrichtigungen mit höchster Priorität prüfen
|
||||
|
||||
Entscheide, welche Art von Benachrichtigungen am dringendsten überprüft werden müssen und wähle einen Zeitpunkt für den Review, der für Dich am besten ist. Du solltest Dir überlegen „Wen blockiere ich?"
|
||||
|
||||
Du kannst dich beispielsweise dazu entscheiden, deine Benachrichtigungen morgens während deiner Tagesplanung in folgender Reihenfolge zu prüfen:
|
||||
- Pull Requests, bei denen dein Review angefordert ist. (Filtere nach `reason:review-requested`.)
|
||||
- Ereignisse, in denen dein Benutzername durch @mentioned erwähnt wird, auch als „direkte Erwähnungen“ bezeichnet. (Filtere nach `reason:mention`.)
|
||||
- Ereignisse, in denen ein Team, dem du angehörst, durch @mentioned erwähnt wird, auch als „Teamerwähnungen“ bezeichnet. (Filtere nach `reason:team-mention`.)
|
||||
- CI-Workflow-Fehler für ein bestimmtest Repository. (Filtere nach `reason:ci-activity` und `repo:owner/repo-name`, und stelle sicher, dass du CI-Aktivitätsbenachrichtigungen für Workflowfehler in deinen Benachrichtigungseinstellungen aktiviert hast.)
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tipp**: Um Benachrichtigungen mit der höchsten Prioritäten schnell zu überprüfen, richte benutzerdefinierte Filter in der Reihenfolge ihrer Überprüfungspriorität ein. Weitere Informationen findest du unter [Verwalten von Benachrichtigungen aus deinem Posteingang](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#customizing-your-inbox-with-custom-filters).
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## Nachverfolgung laufender Benachrichtigungsaktualisierungen
|
||||
|
||||
Um Benachrichtigungen nachzuverfolgen, überlege Dir auch „Über was wurde ich blockiert und bin es nicht mehr?" Wähle dann Die Prioritäten der Nachverfolgung deiner Benachrichtigungen.
|
||||
|
||||
Beispielsweise kannst du folgende Reihenfolge für die Nachverfolgung wählen:
|
||||
- Issues und Pull Requests, denen du zugeordnet bist. Schließe sofort alle möglichen Issues und Pull Requests und füge Aktualisierungen hinzu. Bei Bedarf sicherer Benachrichtigungen für eine spätere Überprüfung.
|
||||
- Überprüfe Benachrichtigungen, die du in deinem Posteingang gesichert hast, vor allem ungelesene Aktualisierungen. Wenn der Thread nicht mehr relevant ist, deaktiviere {% octicon "bookmark" aria-label="The bookmark icon" %}, um die Benachrichtigung aus dem gespeicherten Posteingang zu entfernen, und hebe die Speicherung auf.
|
||||
|
||||
## Benachrichtigungen mit niedriger Priorität verwalten
|
||||
|
||||
Nach der Prüfung der Benachrichtigungen mit höherer Priorität überprüfe nun die verbleibenden Benachrichtigungen, wie beispielsweise Teilnahmebenachrichtigungen. Stellen Sie sich die folgenden Fragen:
|
||||
- Kann ich diese Benachrichtigung abmelden? Ist diese Benachrichtigung abgeschlossen und kann als **Erledigt** gekennzeichnet werden?
|
||||
{% tip %}
|
||||
|
||||
**Tipp**: Wenn du dich von einer Benachrichtigung abmeldest, erhältst du erst dann neue Updates, wenn du am Thread teilzunehmen beginnst oder wenn du oder ein Team, dem du angehörst, über @mentioned erwähnt wird. Wenn du eine Benachrichtigung als **Erledigt** markierst, wird die Benachrichtigung aus der Hauptansicht deines Posteingangs entfernt und kann mit der Abfrage `is:read` angezeigt werden. Weitere Informationen findest du unter [Verwalten von Benachrichtigungen aus deinem Posteingang](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options).
|
||||
|
||||
{% endtip %}
|
||||
- Möchtest du zukünftige Aktualisierungen erhalten, wenn dieser Issue oder Pull Request geschlossen oder wieder geöffnet wird oder wenn ein Pull Request zusammengeführt wird? Weitere Informationen findest du unter [Selektieren einer einzelnen Benachrichtigung](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request).
|
||||
- Möchtest du in Zukunft keine solchen Benachrichtigungen mehr erhalten? Falls ja, erwäge Dich abzumelden. Weitere Informationen findest du unter [Verwalten von Abonnement für Aktivitäten auf GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github).
|
||||
|
||||
## Deine am wenigsten wichtigen Benachrichtigungen löschen
|
||||
|
||||
Wähle aus, welche Art von Benachrichtigungen für Dich am schnellsten und am einfachsten zu selektieren und aus deinem Posteingang zu entfernen sind, wobei du idealerweise mehrere Benachrichtigungen gleichzeitig selektieren kannst.
|
||||
|
||||
Du kannst beispielsweise festlegen, dass Benachrichtigungen in dieser Reihenfolge gelöscht werden sollen:
|
||||
- Teilnahmebenachrichtigungen, von denen du Dich abmelden kannst.
|
||||
- Aktualisierungen von Repositorys, die nicht relevant sind um aufbewahrt oder nachverfolgt zu werden.
|
||||
|
||||
Weitere Informationen zum gleichzeitigen Verwalten mehrerer Benachrichtigungen in deinem Posteingang findest du unter [Verwalten von Benachrichtigungen über deinen Posteingang](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time).
|
||||
|
||||
Du kannst auch erwägen, deine Benachrichtigungseinstellungen zu ändern oder diese Aktualisierungen nach Möglichkeit zu deaktivieren. Weitere Informationen findest du unter [Konfigurieren von Benachrichtigungen](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications) oder unter [Verwalten von Abonnements für Aktivitäten auf GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github).
|
||||
@@ -0,0 +1,27 @@
|
||||
---
|
||||
title: Benachrichtigungen anschauen und selektieren
|
||||
intro: 'Um deinen Workflow für Benachrichtigungen zu optimieren, kannst du anpassen, wie du Benachrichtigungen ansehen und selektieren willst.'
|
||||
redirect_from:
|
||||
- /articles/managing-notifications
|
||||
- /articles/managing-your-notifications
|
||||
- /github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Notifications
|
||||
children:
|
||||
- /managing-notifications-from-your-inbox
|
||||
- /triaging-a-single-notification
|
||||
- /customizing-a-workflow-for-triaging-your-notifications
|
||||
shortTitle: Customize a workflow
|
||||
ms.openlocfilehash: a4130fe6877b7071211494226f67906e2870224b
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145104556'
|
||||
---
|
||||
|
||||
@@ -0,0 +1,181 @@
|
||||
---
|
||||
title: Managing notifications from your inbox
|
||||
intro: 'Use your inbox to quickly triage and sync your notifications across email{% ifversion fpt or ghes or ghec %} and mobile{% endif %}.'
|
||||
redirect_from:
|
||||
- /articles/marking-notifications-as-read
|
||||
- /articles/saving-notifications-for-later
|
||||
- /github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox
|
||||
- /github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Notifications
|
||||
shortTitle: Manage from your inbox
|
||||
---
|
||||
|
||||
## About your inbox
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
{% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)."
|
||||
{% endif %}
|
||||
|
||||
To access your notifications inbox, in the upper-right corner of any page, click {% octicon "bell" aria-label="The notifications bell" %}.
|
||||
|
||||
|
||||
|
||||
Your inbox shows all of the notifications that you haven't unsubscribed to or marked as **Done.** You can customize your inbox to best suit your workflow using filters, viewing all or just unread notifications, and grouping your notifications to get a quick overview.
|
||||
|
||||
|
||||
|
||||
By default, your inbox will show read and unread notifications. To only see unread notifications, click **Unread** or use the `is:unread` query.
|
||||
|
||||
|
||||
|
||||
## Triaging options
|
||||
|
||||
You have several options for triaging notifications from your inbox.
|
||||
|
||||
| Triaging option | Description |
|
||||
|-----------------|-------------|
|
||||
| Save | Saves your notification for later review. To save a notification, to the right of the notification, click {% octicon "bookmark" aria-label="The bookmark icon" %}. <br> <br> Saved notifications are kept indefinitely and can be viewed by clicking **Saved** in the sidebar or with the `is:saved` query. If your saved notification is older than 5 months and becomes unsaved, the notification will disappear from your inbox within a day. |
|
||||
| Done | Marks a notification as completed and removes the notification from your inbox. You can see all completed notifications by clicking **Done** in the sidebar or with the `is:done` query. Notifications marked as **Done** are saved for 5 months.
|
||||
| Unsubscribe | Automatically removes the notification from your inbox and unsubscribes you from the conversation until you are @mentioned, a team you're on is @mentioned, or you're requested for review.
|
||||
| Read | Marks a notification as read. To only view read notifications in your inbox, use the `is:read` query. This query doesn't include notifications marked as **Done**.
|
||||
| Unread | Marks notification as unread. To only view unread notifications in your inbox, use the `is:unread` query. |
|
||||
|
||||
To see the available keyboard shortcuts, see "[Keyboard Shortcuts](/github/getting-started-with-github/keyboard-shortcuts#notifications)."
|
||||
|
||||
Before choosing a triage option, you can preview your notification's details first and investigate. For more information, see "[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification)."
|
||||
|
||||
## Triaging multiple notifications at the same time
|
||||
|
||||
To triage multiple notifications at once, select the relevant notifications and use the {% octicon "kebab-horizontal" aria-label="The edit icon" %} drop-down to choose a triage option.
|
||||
|
||||
|
||||
|
||||
## Default notification filters
|
||||
|
||||
By default, your inbox has filters for when you are assigned, participating in a thread, requested to review a pull request, or when your username is @mentioned directly or a team you're a member of is @mentioned.
|
||||
|
||||
|
||||
|
||||
## Customizing your inbox with custom filters
|
||||
|
||||
You can add up to 15 of your own custom filters.
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
2. To open the filter settings, in the left sidebar, next to "Filters", click {% octicon "gear" aria-label="The Gear icon" %}.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** You can quickly preview a filter's inbox results by creating a query in your inbox view and clicking **Save**, which opens the custom filter settings.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
3. Add a name for your filter and a filter query. For example, to only see notifications for a specific repository, you can create a filter using the query `repo:octocat/open-source-project-name reason:participating`. You can also add emojis with a native emoji keyboard. For a list of supported search queries, see "[Supported queries for custom filters](#supported-queries-for-custom-filters)."
|
||||
|
||||
|
||||
|
||||
4. Click **Create**.
|
||||
|
||||
## Custom filter limitations
|
||||
|
||||
Custom filters do not currently support:
|
||||
- Full text search in your inbox, including searching for pull request or issue titles.
|
||||
- Distinguishing between the `is:issue`, `is:pr`, and `is:pull-request` query filters. These queries will return both issues and pull requests.
|
||||
- Creating more than 15 custom filters.
|
||||
- Changing the default filters or their order.
|
||||
- Search [exclusion](/github/searching-for-information-on-github/understanding-the-search-syntax#exclude-certain-results) using `NOT` or `-QUALIFIER`.
|
||||
|
||||
## Supported queries for custom filters
|
||||
|
||||
These are the types of filters that you can use:
|
||||
- Filter by repository with `repo:`
|
||||
- Filter by discussion type with `is:`
|
||||
- Filter by notification reason with `reason:`{% ifversion fpt or ghec %}
|
||||
- Filter by notification author with `author:`
|
||||
- Filter by organization with `org:`{% endif %}
|
||||
|
||||
### Supported `repo:` queries
|
||||
|
||||
To add a `repo:` filter, you must include the owner of the repository in the query: `repo:owner/repository`. An owner is the organization or the user who owns the {% data variables.product.prodname_dotcom %} asset that triggers the notification. For example, `repo:octo-org/octo-repo` will show notifications triggered in the octo-repo repository within the octo-org organization.
|
||||
|
||||
### Supported `is:` queries
|
||||
|
||||
To filter notifications for specific activity on {% data variables.location.product_location %}, you can use the `is` query. For example, to only see repository invitation updates, use `is:repository-invitation`{% ifversion not ghae %}, and to only see {% data variables.product.prodname_dependabot_alerts %}, use `is:repository-vulnerability-alert`{% endif %}.
|
||||
|
||||
- `is:check-suite`
|
||||
- `is:commit`
|
||||
- `is:gist`
|
||||
- `is:issue-or-pull-request`
|
||||
- `is:release`
|
||||
- `is:repository-invitation`
|
||||
- `is:repository-vulnerability-alert`{% ifversion fpt or ghec %}
|
||||
- `is:repository-advisory`{% endif %}
|
||||
- `is:team-discussion`{% ifversion fpt or ghec %}
|
||||
- `is:discussion`{% endif %}
|
||||
|
||||
For information about reducing noise from notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
|
||||
|
||||
You can also use the `is:` query to describe how the notification was triaged.
|
||||
|
||||
- `is:saved`
|
||||
- `is:done`
|
||||
- `is:unread`
|
||||
- `is:read`
|
||||
|
||||
### Supported `reason:` queries
|
||||
|
||||
To filter notifications by why you've received an update, you can use the `reason:` query. For example, to see notifications when you (or a team you're on) is requested to review a pull request, use `reason:review-requested`. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)."
|
||||
|
||||
| Query | Description |
|
||||
|-----------------|-------------|
|
||||
| `reason:assign` | When there's an update on an issue or pull request you've been assigned to.
|
||||
| `reason:author` | When you opened a pull request or issue and there has been an update or new comment.
|
||||
| `reason:comment`| When you commented on an issue, pull request, or team discussion.
|
||||
| `reason:participating` | When you have commented on an issue, pull request, or team discussion or you have been @mentioned.
|
||||
| `reason:invitation` | When you're invited to a team, organization, or repository.
|
||||
| `reason:manual` | When you click **Subscribe** on an issue or pull request you weren't already subscribed to.
|
||||
| `reason:mention` | You were directly @mentioned.
|
||||
| `reason:review-requested` | You or a team you're on have been requested to review a pull request.
|
||||
| `reason:security-alert` | When a security alert is issued for a repository.
|
||||
| `reason:state-change` | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged.
|
||||
| `reason:team-mention` | When a team you're a member of is @mentioned.
|
||||
| `reason:ci-activity` | When a repository has a CI update, such as a new workflow run status.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### Supported `author:` queries
|
||||
|
||||
To filter notifications by user, you can use the `author:` query. An author is the original author of the thread (issue, pull request, gist, discussions, and so on) for which you are being notified. For example, to see notifications for threads created by the Octocat user, use `author:octocat`.
|
||||
|
||||
### Supported `org:` queries
|
||||
|
||||
To filter notifications by organization, you can use the `org` query. The organization you need to specify in the query is the organization of the repository for which you are being notified on {% data variables.product.prodname_dotcom %}. This query is useful if you belong to several organizations, and want to see notifications for a specific organization.
|
||||
|
||||
For example, to see notifications from the octo-org organization, use `org:octo-org`.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## {% data variables.product.prodname_dependabot %} custom filters
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
If you use {% data variables.product.prodname_dependabot %} to keep your dependencies up-to-date, you can use and save these custom filters:
|
||||
- `is:repository_vulnerability_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %}.
|
||||
- `reason:security_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %} and security update pull requests.
|
||||
- `author:app/dependabot` to show notifications generated by {% data variables.product.prodname_dependabot %}. This includes {% data variables.product.prodname_dependabot_alerts %}, security update pull requests, and version update pull requests.
|
||||
|
||||
For more information about {% data variables.product.prodname_dependabot %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
If you use {% data variables.product.prodname_dependabot %} to tell you about insecure dependencies, you can use and save these custom filters to show notifications for {% data variables.product.prodname_dependabot_alerts %}:
|
||||
- `is:repository_vulnerability_alert`
|
||||
- `reason:security_alert`
|
||||
|
||||
For more information about {% data variables.product.prodname_dependabot %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
|
||||
{% endif %}
|
||||
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
title: Eine einzige Benachrichtigung selektieren
|
||||
intro: 'Wenn du eine einzelne Benachrichtigung überprüfen und untersuchen willst, hast Du verschiedene Auswahlmöglichkeiten, die für die detaillierte Benachrichtigungs-Ansicht optimiert sind.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Notifications
|
||||
redirect_from:
|
||||
- /github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification
|
||||
- /github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/triaging-a-single-notification
|
||||
shortTitle: Triage a notification
|
||||
ms.openlocfilehash: c81cc30449dd1b37a58df0b91a036fbd629d8ae3
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145104552'
|
||||
---
|
||||
## Sichern einer einzelnen Benachrichtigung
|
||||
|
||||
Um eine einzelne Benachrichtigung zum späteren Review zu sichern, klicke rechts neben der Benachrichtigung auf {% octicon "bookmark" aria-label="The bookmark icon" %}. Du kannst nur eine Benachrichtigung nach der Anderen sichern.
|
||||
|
||||
Gespeicherte Benachrichtigungen werden unbegrenzt aufbewahrt und können angezeigt werden, indem du in der Randleiste auf **Gespeichert** klickst, oder mit der `is:saved`-Abfrage. Wenn Deine gesicherte Benachrichtigung älter als 5 Monate ist und Du sie nicht mehr sicherst, wird die Benachrichtigung innerhalb eines Tages aus Deinem Posteingang entfernt.
|
||||
|
||||
|
||||
|
||||
## Eine Benachrichtigung untersuchen
|
||||
|
||||
Wenn Du eine individuelle Benachrichtigung aus Deinem Posteingang anklickst, wirst Du an die Unterhaltung weitergeleitet, die die Benachrichtigung ausgelöst hat. Oben auf der Seite kannst Du:
|
||||
- Die einzelne Benachrichtigung als erledigt markieren
|
||||
- Künftige Benachrichtigungen abmelden
|
||||
- Die Benachrichtigung als gelesen markieren
|
||||
- Die Benachrichtigung für später sichern
|
||||
- Zu Deinem Postfach für Benachrichtigungen zurück gehen
|
||||
|
||||
Weitere Informationen zu deinen Selektierungsoptionen findest du unter [Verwalten von Benachrichtigungen aus Ihrem Posteingang](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options).
|
||||
|
||||
## Anpassen, wann künftige Aktualisierungen für einen Issue oder Pull Request erhalten werden sollen
|
||||
|
||||
Du kannst wählen, wie Du zukünftige Benachrichtigungen für einen spezifischen Issue oder einen Pull Request erhalten willst.
|
||||
|
||||
1. Klicke in der rechten Spalte des Issues oder Pull Requests neben „Benachrichtigungen“ auf **Anpassen**.
|
||||
|
||||
|
||||
|
||||
2. Wähle **Benutzerdefiniert** und entscheide, wann du ein Benachrichtigungsupdate für diesen Thread erhalten möchtest. Du kannst zum Beispiel wählen, ob Du eine Aktualisierung erhältst, wenn der Pull Request zusammengeführt, geschlossen oder wieder geöffnet wurde. Du bist wieder Abonnent, wenn du am Thread teilnimmst, dein Benutzername @mentioned wird oder ein Team, in dem Du Mitglied bist, @mentioned wird.
|
||||
|
||||
|
||||
|
||||
3. Klicken Sie auf **Speichern**.
|
||||
@@ -0,0 +1,35 @@
|
||||
---
|
||||
title: About your organization's profile
|
||||
intro: Your organization's profile page shows basic information about your organization.
|
||||
redirect_from:
|
||||
- /articles/about-your-organization-s-profile
|
||||
- /articles/about-your-organizations-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/about-your-organizations-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
shortTitle: Organization's profile
|
||||
---
|
||||
|
||||
You can optionally choose to add a description, location, website, and email address for your organization, and pin important repositories.{% ifversion fpt or ghec or ghes > 3.3 %} You can customize your organization's public profile by adding a README.md file. For more information, see "[Customizing your organization's profile](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)."{% endif %}
|
||||
|
||||
{% ifversion fpt %}
|
||||
Organizations that use {% data variables.product.prodname_ghe_cloud %} can confirm their organization's identity and display a "Verified" badge on their organization's profile page by verifying the organization's domains with {% data variables.product.product_name %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" in the {% data variables.product.prodname_ghe_cloud %} documenatation.
|
||||
{% elsif ghec or ghes %}
|
||||
To confirm your organization's identity and display a "Verified" badge on your organization profile page, you can verify your organization's domains with {% data variables.product.prodname_dotcom %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)"
|
||||
@@ -0,0 +1,49 @@
|
||||
---
|
||||
title: Informationen zu deinem Profil
|
||||
intro: 'Deine Profilseite erzählt anderen die Geschichte deiner Arbeit anhand der Repositorys, an denen du interessiert bist, anhand deiner Beiträge und anhand der Unterhaltungen, die du geführt hast.'
|
||||
redirect_from:
|
||||
- /articles/viewing-your-feeds
|
||||
- /articles/profile-pages
|
||||
- /articles/about-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/about-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
ms.openlocfilehash: e27e14102b4f57e9eb50266c5c271a2f6bb3892c
|
||||
ms.sourcegitcommit: bf11c3e08cbb5eab6320e0de35b32ade6d863c03
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 10/27/2022
|
||||
ms.locfileid: '148111616'
|
||||
---
|
||||
Du kannst persönliche Informationen über Dich selbst in deiner Bio hinzufügen, beispielsweise über frühere Orte, an denen du gearbeitet hast, Projekte, an denen du mitgewirkt hast, oder Interessen, die du hast, von denen andere Personen möglicherweise wissen möchten. Weitere Informationen findest du unter "[Hinzufügen eines Lebenslaufs zu deinem Profil](/articles/personalizing-your-profile/#adding-a-bio-to-your-profile)".
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
{% data reusables.profile.profile-readme %}
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
Personen, die dein Profil aufrufen, sehen eine Zeitleiste deiner Beitragsaktivitäten, wie Issues und Pull Requests, die du geöffnet hast, Commits, die du durchgeführt hast, und Pull Requests, deren Review du durchgeführt hast. Du kannst wählen, ob du nur öffentliche Beiträge anzeigen oder auch private, anonymisierte Beiträge einbeziehen möchtest. Weitere Informationen findest du unter "[Anzeigen von Beiträgen auf deiner Profilseite](/articles/viewing-contributions-on-your-profile-page)" oder "[Veröffentlichen oder Ausblenden deiner privaten Beiträge in deinem Profil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)".
|
||||
|
||||
Personen, die dein Profil besuchen, sehen auch die folgenden Informationen.
|
||||
|
||||
- Repositorys und Gists, die du besitzt oder zu denen du beiträgst. {% ifversion fpt or ghes or ghec %}Du kannst deine beste Arbeit präsentieren, indem du Repositorys und Gists an dein Profil anheftest. Weitere Informationen findest du unter "[Anheften von Elementen an dein Profil](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)."{% endif %}
|
||||
- Repositorys, die du mit einem Stern versehen{% ifversion fpt or ghec %} und in Listen organisiert{% endif %} hast. Weitere Informationen findest du unter [Speichern von Repositorys mit Sternen](/articles/saving-repositories-with-stars/).
|
||||
- Eine Übersicht über deine Aktivitäten in den Organisationen, Repositorys und Teams, in denen du am meisten aktiv bist. Weitere Informationen findest du unter [Anzeigen einer Aktivitätsübersicht auf deinem Profil](/articles/showing-an-overview-of-your-activity-on-your-profile).{% ifversion fpt or ghec %}
|
||||
- Badges und Erfolge, die deine Aktivitäten hervorheben und anzeigen, wenn du {% data variables.product.prodname_pro %} verwendest oder an Programmen wie dem {% data variables.product.prodname_arctic_vault %}-, dem {% data variables.product.prodname_sponsors %}- oder dem {% data variables.product.company_short %}-Entwicklerprogramm teilnimmst. Weitere Informationen findest du unter "[Personalisieren deines Profils](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)."{% endif %}
|
||||
|
||||
Du kannst auch einen Status auf deinem Profil einstellen, um Angaben zu deiner Verfügbarkeit zu machen. Weitere Informationen findest du unter "[Festlegen eines Status](/articles/personalizing-your-profile/#setting-a-status)".
|
||||
|
||||
## Weitere Informationsquellen
|
||||
|
||||
- "[Wie richte ich mein Profilbild ein?](/articles/how-do-i-set-up-my-profile-picture)"
|
||||
- "[Veröffentlichen oder Ausblenden deiner privaten Beiträge auf deinem Profil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)"
|
||||
- [Anzeigen von Beiträge auf deinem Profil](/articles/viewing-contributions-on-your-profile)
|
||||
@@ -0,0 +1,28 @@
|
||||
---
|
||||
title: Ihr Profil anpassen
|
||||
intro: 'Du kannst Dein Profil anpassen, damit andere Benutzer sich ein besseres Bild von Deiner Person und Deiner Arbeit machen können.'
|
||||
redirect_from:
|
||||
- /articles/customizing-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/customizing-your-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
children:
|
||||
- /about-your-profile
|
||||
- /about-your-organizations-profile
|
||||
- /personalizing-your-profile
|
||||
- /managing-your-profile-readme
|
||||
- /pinning-items-to-your-profile
|
||||
- /setting-your-profile-to-private
|
||||
ms.openlocfilehash: 617625a9e51fa44f5f1e291b5c3828b1c403b5bc
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145105192'
|
||||
---
|
||||
|
||||
@@ -0,0 +1,77 @@
|
||||
---
|
||||
title: Managing your profile README
|
||||
intro: 'You can add a README to your {% data variables.product.prodname_dotcom %} profile to tell other people about yourself.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-your-profile-readme
|
||||
- /github/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme
|
||||
shortTitle: Your profile README
|
||||
---
|
||||
## About your profile README
|
||||
|
||||
You can share information about yourself with the community on {% data variables.location.product_location %} by creating a profile README. {% data variables.product.prodname_dotcom %} shows your profile README at the top of your profile page.
|
||||
|
||||
You decide what information to include in your profile README, so you have full control over how you present yourself on {% data variables.product.prodname_dotcom %}. Here are some examples of information that visitors may find interesting, fun, or useful in your profile README.
|
||||
|
||||
- An "About me" section that describes your work and interests
|
||||
- Contributions you're proud of, and context about those contributions
|
||||
- Guidance for getting help in communities where you're involved
|
||||
|
||||
|
||||
|
||||
You can format text and include emoji, images, and GIFs in your profile README by using {% data variables.product.company_short %} Flavored Markdown. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)." For a hands-on guide to customizing your profile README, see "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)."
|
||||
|
||||
## Prerequisites
|
||||
|
||||
GitHub will display your profile README on your profile page if all of the following are true.
|
||||
|
||||
- You've created a repository with a name that matches your {% data variables.product.prodname_dotcom %} username.
|
||||
- The repository is public.
|
||||
- The repository contains a file named README.md in its root.
|
||||
- The README.md file contains any content.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: If you created a public repository with the same name as your username before July 2020, {% data variables.product.prodname_dotcom %} won't automatically show the repository's README on your profile. You can manually share the repository's README to your profile by going to the repository on {% data variables.product.prodname_dotcom_the_website %} and clicking **Share to profile**.
|
||||
|
||||
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Adding a profile README
|
||||
|
||||
{% data reusables.repositories.create_new %}
|
||||
2. Under "Repository name", type a repository name that matches your {% data variables.product.prodname_dotcom %} username. For example, if your username is "octocat", the repository name must be "octocat".
|
||||
|
||||
3. Optionally, add a description of your repository. For example, "My personal repository."
|
||||
|
||||
4. Select **Public**.
|
||||
|
||||
{% data reusables.repositories.initialize-with-readme %}
|
||||
{% data reusables.repositories.create-repo %}
|
||||
7. Above the right sidebar, click **Edit README**.
|
||||
|
||||
|
||||
The generated README file is pre-populated with a template to give you some inspiration for your profile README.
|
||||
|
||||
|
||||
For a summary of all the available emojis and their codes, see "[Emoji cheat sheet](https://www.webfx.com/tools/emoji-cheat-sheet/)."
|
||||
|
||||
## Removing a profile README
|
||||
|
||||
The profile README is removed from your {% data variables.product.prodname_dotcom %} profile if any of the following apply:
|
||||
|
||||
- The README file is empty or doesn't exist.
|
||||
- The repository is private.
|
||||
- The repository name no longer matches your username.
|
||||
|
||||
The method you choose depends upon your needs, but if you're unsure, we recommend making your repository private. For steps on how to make your repository private, see "[Changing a repository's visibility](/github/administering-a-repository/setting-repository-visibility#changing-a-repositorys-visibility)."
|
||||
|
||||
## Further reading
|
||||
|
||||
- [About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)
|
||||
@@ -0,0 +1,273 @@
|
||||
---
|
||||
title: Personalizing your profile
|
||||
intro: 'You can share information about yourself with other {% data variables.product.product_name %} users by setting a profile picture and adding a bio to your profile.'
|
||||
redirect_from:
|
||||
- /articles/adding-a-bio-to-your-profile
|
||||
- /articles/setting-your-profile-picture
|
||||
- /articles/how-do-i-set-up-my-profile-picture
|
||||
- /articles/gravatar-problems
|
||||
- /articles/how-do-i-set-up-my-avatar
|
||||
- /articles/personalizing-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/personalizing-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
shortTitle: Personalize
|
||||
---
|
||||
## Changing your profile picture
|
||||
|
||||
Your profile picture helps identify you across {% data variables.product.product_name %} in pull requests, comments, contributions pages, and graphs.
|
||||
|
||||
When you sign up for an account, {% data variables.product.product_name %} provides you with a randomly generated "identicon". [Your identicon](https://github.com/blog/1586-identicons) generates from a hash of your user ID, so there's no way to control its color or pattern. You can replace your identicon with an image that represents you.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note{% ifversion ghec %}s{% endif %}**: {% ifversion ghec %}
|
||||
|
||||
* {% endif %}Your profile picture should be a PNG, JPG, or GIF file, and it must be less than 1 MB in size and smaller than 3000 by 3000 pixels. For the best quality rendering, we recommend keeping the image at about 500 by 500 pixels.
|
||||
{% ifversion ghec %}* Gravatar profile pictures are not supported with {% data variables.product.prodname_emus %}.{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Setting a profile picture
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
|
||||
|
||||
3. Click **Upload a photo...**.{% ifversion not ghae %}
|
||||
{% endif %}
|
||||
3. Crop your picture. When you're done, click **Set new profile picture**.
|
||||
|
||||
|
||||
### Resetting your profile picture to the identicon
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
|
||||
|
||||
3. To revert to your identicon, click **Remove photo**. {% ifversion not ghae %}If your email address is associated with a [Gravatar](https://en.gravatar.com/), you cannot revert to your identicon. Click **Revert to Gravatar** instead.
|
||||
{% endif %}
|
||||
|
||||
## Changing your profile name
|
||||
|
||||
You can change the name that is displayed on your profile. This name may also be displayed next to comments you make on private repositories owned by an organization. For more information, see "[Managing the display of member names in your organization](/articles/managing-the-display-of-member-names-in-your-organization)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% note %}
|
||||
|
||||
**Note:** If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, any changes to your profile name must be made through your identity provider instead of {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %}
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
2. Under "Name", type the name you want to be displayed on your profile.
|
||||
|
||||
|
||||
## Adding a bio to your profile
|
||||
|
||||
Add a bio to your profile to share information about yourself with other {% data variables.product.product_name %} users. With the help of [@mentions](/articles/basic-writing-and-formatting-syntax) and emoji, you can include information about where you currently or have previously worked, what type of work you do, or even what kind of coffee you drink.
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
For a longer-form and more prominent way of displaying customized information about yourself, you can also use a profile README. For more information, see "[Managing your profile README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:**
|
||||
If you have the activity overview section enabled for your profile and you @mention an organization you're a member of in your profile bio, then that organization will be featured first in your activity overview. For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
2. Under **Bio**, add the content that you want displayed on your profile. The bio field is limited to 160 characters.
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** When you @mention an organization, only those that you're a member of will autocomplete. You can still @mention organizations that you're not a member of, like a previous employer, but the organization name won't autocomplete for you.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% data reusables.profile.update-profile %}
|
||||
|
||||
{% ifversion profile-time-zone %}
|
||||
|
||||
## Setting your location and time zone
|
||||
|
||||
You can set a location and time zone on your profile to show other people your local time. Your location and time zone will be visible:
|
||||
- on your {% data variables.product.product_name %} profile page.
|
||||
- when people hover over your username or avatar on {% data variables.product.product_name %}.
|
||||
|
||||
When you view your profile, you will see your location, local time, and your time zone in relation to Universal Time Coordinated.
|
||||
|
||||
|
||||
|
||||
When others view your profile, they will see your location, local time, and the time difference in hours from their own local time.
|
||||
|
||||
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
1. Under **Location**, type the location you want to be displayed on your profile.
|
||||
|
||||
|
||||
|
||||
1. Optionally, to display the current local time on your profile, select **Display current local time**.
|
||||
|
||||
|
||||
|
||||
- Select the **Time zone** dropdown menu, then click your local time zone.
|
||||
|
||||
|
||||
|
||||
{% data reusables.profile.update-profile %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Setting a status
|
||||
|
||||
You can set a status to display information about your current availability on {% data variables.product.product_name %}. Your status will show:
|
||||
- on your {% data variables.product.product_name %} profile page.
|
||||
- when people hover over your username or avatar on {% data variables.product.product_name %}.
|
||||
- on a team page for a team where you're a team member. For more information, see "[About teams](/articles/about-teams/#team-pages)."
|
||||
- on the organization dashboard in an organization where you're a member. For more information, see "[About your organization dashboard](/articles/about-your-organization-dashboard/)."
|
||||
|
||||
When you set your status, you can also let people know that you have limited availability on {% data variables.product.product_name %}.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
If you select the "Busy" option, when people @mention your username, assign you an issue or pull request, or request a pull request review from you, a note next to your username will show that you're busy. You will also be excluded from automatic review assignment for pull requests assigned to any teams you belong to. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."
|
||||
|
||||
1. In the top right corner of {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, click your profile photo, then click **Set status** or, if you already have a status set, click your current status.
|
||||
|
||||
2. To add custom text to your status, click in the text field and type a status message.
|
||||
|
||||
3. Optionally, to set an emoji status, click the smiley icon and select an emoji from the list.
|
||||
|
||||
4. Optionally, if you'd like to share that you have limited availability, select "Busy."
|
||||
|
||||
5. Use the **Clear status** drop-down menu, and select when you want your status to expire. If you don't select a status expiration, you will keep your status until you clear or edit your status.
|
||||
|
||||
6. Use the drop-down menu and click the organization you want your status visible to. If you don't select an organization, your status will be public.
|
||||
|
||||
7. Click **Set status**.
|
||||
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## Displaying badges on your profile
|
||||
|
||||
When you participate in certain programs, {% data variables.product.prodname_dotcom %} automatically displays a badge on your profile.
|
||||
|
||||
| Badge | Program | Description |
|
||||
| --- | --- | --- |
|
||||
| {% octicon "cpu" aria-label="The Developer Program icon" %} | **Developer Program Member** | If you're a registered member of the {% data variables.product.prodname_dotcom %} Developer Program, building an app with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, you'll get a Developer Program Member badge on your profile. For more information on the {% data variables.product.prodname_dotcom %} Developer Program, see [GitHub Developer](/program/). |
|
||||
| {% octicon "star-fill" aria-label="The star icon" %} | **Pro** | If you use {% data variables.product.prodname_pro %} you'll get a PRO badge on your profile. For more information about {% data variables.product.prodname_pro %}, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products#github-pro)." |
|
||||
| {% octicon "lock" aria-label="The lock icon" %} | **Security Bug Bounty Hunter** | If you helped out hunting down security vulnerabilities, you'll get a Security Bug Bounty Hunter badge on your profile. For more information about the {% data variables.product.prodname_dotcom %} Security program, see [{% data variables.product.prodname_dotcom %} Security](https://bounty.github.com/). |
|
||||
| {% octicon "mortar-board" aria-label="The mortar-board icon" %} | **{% data variables.product.prodname_dotcom %} Campus Expert** | If you participate in the {% data variables.product.prodname_campus_program %}, you will get a {% data variables.product.prodname_dotcom %} Campus Expert badge on your profile. For more information about the Campus Experts program, see [Campus Experts](https://education.github.com/experts). |
|
||||
| {% octicon "shield" aria-label="The shield icon" %} | **Security advisory credit** | If a security advisory you submit to the [{% data variables.product.prodname_dotcom %} Advisory Database](https://github.com/advisories) is accepted, you'll get a Security advisory credit badge on your profile. For more information about {% data variables.product.prodname_dotcom %} Security Advisories, see [{% data variables.product.prodname_dotcom %} Security Advisories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories). |
|
||||
| {% octicon "check" aria-label="The check icon" %} | **Discussion answered** | If your reply to a discussion is marked as the answer, you'll get a Discussion answered badge on your profile. For more information about {% data variables.product.prodname_dotcom %} Discussions, see [About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions). |
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
## Earning Achievements
|
||||
|
||||
Achievements celebrate specific events and actions that happen on {% data variables.product.prodname_dotcom %}. They will appear as small badges listed in the sidebar of your profile. Clicking or hovering on an achievement will show a detailed view that hints at how the achievement was earned, with a short description and links to the contributing events. The event links will only be visible to users that have access to the repository or organization that the event took place in. Event links will appear inaccessible to all users without access.
|
||||
|
||||
To stop private contributions from counting toward your Achievements, or to turn off Achievements entirely, see "[Showing your private contributions and Achievements on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** This feature is currently in beta and subject to change.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## List of qualifying repositories for Mars 2020 Helicopter Contributor achievement
|
||||
|
||||
If you authored any commit(s) present in the commit history for the listed tag of one or more of the repositories below, you'll receive the Mars 2020 Helicopter Contributor achievement on your profile. The authored commit must be with a verified email address, associated with your account at the time {% data variables.product.prodname_dotcom %} determined the eligible contributions, in order to be attributed to you. You can be the original author or [one of the co-authors](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors) of the commit. Future changes to verified emails will not have an effect on the badge. We built the list based on information received from NASA's Jet Propulsion Laboratory.
|
||||
|
||||
| {% data variables.product.prodname_dotcom %} Repository | Version | Tag |
|
||||
|---|---|---|
|
||||
| [torvalds/linux](https://github.com/torvalds/linux) | 3.4 | [v3.4](https://github.com/torvalds/linux/releases/tag/v3.4) |
|
||||
| [python/cpython](https://github.com/python/cpython) | 3.9.2 | [v3.9.2](https://github.com/python/cpython/releases/tag/v3.9.2) |
|
||||
| [boto/boto3](https://github.com/boto/boto3) | 1.17.17 | [1.17.17](https://github.com/boto/boto3/releases/tag/1.17.17) |
|
||||
| [boto/botocore](https://github.com/boto/botocore) | 1.20.11 | [1.20.11](https://github.com/boto/botocore/releases/tag/1.20.11) |
|
||||
| [certifi/python-certifi](https://github.com/certifi/python-certifi) | 2020.12.5 | [2020.12.05](https://github.com/certifi/python-certifi/releases/tag/2020.12.05) |
|
||||
| [chardet/chardet](https://github.com/chardet/chardet) | 4.0.0 | [4.0.0](https://github.com/chardet/chardet/releases/tag/4.0.0) |
|
||||
| [matplotlib/cycler](https://github.com/matplotlib/cycler) | 0.10.0 | [v0.10.0](https://github.com/matplotlib/cycler/releases/tag/v0.10.0) |
|
||||
| [elastic/elasticsearch-py](https://github.com/elastic/elasticsearch-py) | 6.8.1 | [6.8.1](https://github.com/elastic/elasticsearch-py/releases/tag/6.8.1) |
|
||||
| [ianare/exif-py](https://github.com/ianare/exif-py) | 2.3.2 | [2.3.2](https://github.com/ianare/exif-py/releases/tag/2.3.2) |
|
||||
| [kjd/idna](https://github.com/kjd/idna) | 2.10 | [v2.10](https://github.com/kjd/idna/releases/tag/v2.10) |
|
||||
| [jmespath/jmespath.py](https://github.com/jmespath/jmespath.py) | 0.10.0 | [0.10.0](https://github.com/jmespath/jmespath.py/releases/tag/0.10.0) |
|
||||
| [nucleic/kiwi](https://github.com/nucleic/kiwi) | 1.3.1 | [1.3.1](https://github.com/nucleic/kiwi/releases/tag/1.3.1) |
|
||||
| [matplotlib/matplotlib](https://github.com/matplotlib/matplotlib) | 3.3.4 | [v3.3.4](https://github.com/matplotlib/matplotlib/releases/tag/v3.3.4) |
|
||||
| [numpy/numpy](https://github.com/numpy/numpy) | 1.20.1 | [v1.20.1](https://github.com/numpy/numpy/releases/tag/v1.20.1) |
|
||||
| [opencv/opencv-python](https://github.com/opencv/opencv-python) | 4.5.1.48 | [48](https://github.com/opencv/opencv-python/releases/tag/48) |
|
||||
| [python-pillow/Pillow](https://github.com/python-pillow/Pillow) | 8.1.0 | [8.1.0](https://github.com/python-pillow/Pillow/releases/tag/8.1.0) |
|
||||
| [pycurl/pycurl](https://github.com/pycurl/pycurl) | 7.43.0.6 | [REL_7_43_0_6](https://github.com/pycurl/pycurl/releases/tag/REL_7_43_0_6) |
|
||||
| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing) | 2.4.7 | [pyparsing_2.4.7](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.7) |
|
||||
| [pyserial/pyserial](https://github.com/pyserial/pyserial) | 3.5 | [v3.5](https://github.com/pyserial/pyserial/releases/tag/v3.5) |
|
||||
| [dateutil/dateutil](https://github.com/dateutil/dateutil) | 2.8.1 | [2.8.1](https://github.com/dateutil/dateutil/releases/tag/2.8.1) |
|
||||
| [yaml/pyyaml ](https://github.com/yaml/pyyaml) | 5.4.1 | [5.4.1](https://github.com/yaml/pyyaml/releases/tag/5.4.1) |
|
||||
| [psf/requests](https://github.com/psf/requests) | 2.25.1 | [v2.25.1](https://github.com/psf/requests/releases/tag/v2.25.1) |
|
||||
| [boto/s3transfer](https://github.com/boto/s3transfer) | 0.3.4 | [0.3.4](https://github.com/boto/s3transfer/releases/tag/0.3.4) |
|
||||
| [enthought/scimath](https://github.com/enthought/scimath) | 4.2.0 | [4.2.0](https://github.com/enthought/scimath/releases/tag/4.2.0) |
|
||||
| [scipy/scipy](https://github.com/scipy/scipy) | 1.6.1 | [v1.6.1](https://github.com/scipy/scipy/releases/tag/v1.6.1) |
|
||||
| [benjaminp/six](https://github.com/benjaminp/six) | 1.15.0 | [1.15.0](https://github.com/benjaminp/six/releases/tag/1.15.0) |
|
||||
| [enthought/traits](https://github.com/enthought/traits) | 6.2.0 | [6.2.0](https://github.com/enthought/traits/releases/tag/6.2.0) |
|
||||
| [urllib3/urllib3](https://github.com/urllib3/urllib3) | 1.26.3 | [1.26.3](https://github.com/urllib3/urllib3/releases/tag/1.26.3) |
|
||||
| [python-attrs/attrs](https://github.com/python-attrs/attrs) | 19.3.0 | [19.3.0](https://github.com/python-attrs/attrs/releases/tag/19.3.0) |
|
||||
| [CheetahTemplate3/cheetah3](https://github.com/CheetahTemplate3/cheetah3/) | 3.2.4 | [3.2.4](https://github.com/CheetahTemplate3/cheetah3/releases/tag/3.2.4) |
|
||||
| [pallets/click](https://github.com/pallets/click) | 7.0 | [7.0](https://github.com/pallets/click/releases/tag/7.0) |
|
||||
| [pallets/flask](https://github.com/pallets/flask) | 1.1.1 | [1.1.1](https://github.com/pallets/flask/releases/tag/1.1.1) |
|
||||
| [flask-restful/flask-restful](https://github.com/flask-restful/flask-restful) | 0.3.7 | [0.3.7](https://github.com/flask-restful/flask-restful/releases/tag/0.3.7) |
|
||||
| [pytest-dev/iniconfig](https://github.com/pytest-dev/iniconfig) | 1.0.0 | [v1.0.0](https://github.com/pytest-dev/iniconfig/releases/tag/v1.0.0) |
|
||||
| [pallets/itsdangerous](https://github.com/pallets/itsdangerous) | 1.1.0 | [1.1.0](https://github.com/pallets/itsdangerous/releases/tag/1.1.0) |
|
||||
| [pallets/jinja](https://github.com/pallets/jinja) | 2.10.3 | [2.10.3](https://github.com/pallets/jinja/releases/tag/2.10.3) |
|
||||
| [lxml/lxml](https://github.com/lxml/lxml) | 4.4.1 | [lxml-4.4.1](https://github.com/lxml/lxml/releases/tag/lxml-4.4.1) |
|
||||
| [Python-Markdown/markdown](https://github.com/Python-Markdown/markdown) | 3.1.1 | [3.1.1](https://github.com/Python-Markdown/markdown/releases/tag/3.1.1) |
|
||||
| [pallets/markupsafe](https://github.com/pallets/markupsafe) | 1.1.1 | [1.1.1](https://github.com/pallets/markupsafe/releases/tag/1.1.1) |
|
||||
| [pypa/packaging](https://github.com/pypa/packaging) | 19.2 | [19.2](https://github.com/pypa/packaging/releases/tag/19.2) |
|
||||
| [pexpect/pexpect](https://github.com/pexpect/pexpect) | 4.7.0 | [4.7.0](https://github.com/pexpect/pexpect/releases/tag/4.7.0) |
|
||||
| [pytest-dev/pluggy](https://github.com/pytest-dev/pluggy) | 0.13.0 | [0.13.0](https://github.com/pytest-dev/pluggy/releases/tag/0.13.0) |
|
||||
| [pexpect/ptyprocess](https://github.com/pexpect/ptyprocess) | 0.6.0 | [0.6.0](https://github.com/pexpect/ptyprocess/releases/tag/0.6.0) |
|
||||
| [pytest-dev/py](https://github.com/pytest-dev/py) | 1.8.0 | [1.8.0](https://github.com/pytest-dev/py/releases/tag/1.8.0) |
|
||||
| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing) | 2.4.5 | [pyparsing_2.4.5](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.5) |
|
||||
| [pytest-dev/pytest](https://github.com/pytest-dev/pytest) | 5.3.0 | [5.3.0](https://github.com/pytest-dev/pytest/releases/tag/5.3.0) |
|
||||
| [stub42/pytz](https://github.com/stub42/pytz) | 2019.3 | [release_2019.3](https://github.com/stub42/pytz/releases/tag/release_2019.3) |
|
||||
| [uiri/toml](https://github.com/uiri/toml) | 0.10.0 | [0.10.0](https://github.com/uiri/toml/releases/tag/0.10.0) |
|
||||
| [pallets/werkzeug](https://github.com/pallets/werkzeug) | 0.16.0 | [0.16.0](https://github.com/pallets/werkzeug/releases/tag/0.16.0) |
|
||||
| [dmnfarrell/tkintertable](https://github.com/dmnfarrell/tkintertable) | 1.2 | [v1.2](https://github.com/dmnfarrell/tkintertable/releases/tag/v1.2) |
|
||||
| [wxWidgets/wxPython-Classic](https://github.com/wxWidgets/wxPython-Classic) | 2.9.1.1 | [wxPy-2.9.1.1](https://github.com/wxWidgets/wxPython-Classic/releases/tag/wxPy-2.9.1.1) |
|
||||
| [nasa/fprime](https://github.com/nasa/fprime) | 1.3 | [NASA-v1.3](https://github.com/nasa/fprime/releases/tag/NASA-v1.3) |
|
||||
| [nucleic/cppy](https://github.com/nucleic/cppy) | 1.1.0 | [1.1.0](https://github.com/nucleic/cppy/releases/tag/1.1.0) |
|
||||
| [opencv/opencv](https://github.com/opencv/opencv) | 4.5.1 | [4.5.1](https://github.com/opencv/opencv/releases/tag/4.5.1) |
|
||||
| [curl/curl](https://github.com/curl/curl) | 7.72.0 | [curl-7_72_0](https://github.com/curl/curl/releases/tag/curl-7_72_0) |
|
||||
| [madler/zlib](https://github.com/madler/zlib) | 1.2.11 | [v1.2.11](https://github.com/madler/zlib/releases/tag/v1.2.11) |
|
||||
| [apache/lucene](https://github.com/apache/lucene) | 7.7.3 | [releases/lucene-solr/7.7.3](https://github.com/apache/lucene/releases/tag/releases%2Flucene-solr%2F7.7.3) |
|
||||
| [yaml/libyaml](https://github.com/yaml/libyaml) | 0.2.5 | [0.2.5](https://github.com/yaml/libyaml/releases/tag/0.2.5) |
|
||||
| [elastic/elasticsearch](https://github.com/elastic/elasticsearch) | 6.8.1 | [v6.8.1](https://github.com/elastic/elasticsearch/releases/tag/v6.8.1) |
|
||||
| [twbs/bootstrap](https://github.com/twbs/bootstrap) | 4.3.1 | [v4.3.1](https://github.com/twbs/bootstrap/releases/tag/v4.3.1) |
|
||||
| [vuejs/vue](https://github.com/vuejs/vue) | 2.6.10 | [v2.6.10](https://github.com/vuejs/vue/releases/tag/v2.6.10) |
|
||||
| [carrotsearch/hppc](https://github.com/carrotsearch/hppc) | 0.7.1 | [0.7.1](https://github.com/carrotsearch/hppc/releases/tag/0.7.1) |
|
||||
| [JodaOrg/joda-time](https://github.com/JodaOrg/joda-time) | 2.10.1 | [v2.10.1](https://github.com/JodaOrg/joda-time/releases/tag/v2.10.1) |
|
||||
| [tdunning/t-digest](https://github.com/tdunning/t-digest) | 3.2 | [t-digest-3.2](https://github.com/tdunning/t-digest/releases/tag/t-digest-3.2) |
|
||||
| [HdrHistogram/HdrHistogram](https://github.com/HdrHistogram/HdrHistogram) | 2.1.9 | [HdrHistogram-2.1.9](https://github.com/HdrHistogram/HdrHistogram/releases/tag/HdrHistogram-2.1.9) |
|
||||
| [locationtech/spatial4j](https://github.com/locationtech/spatial4j) | 0.7 | [spatial4j-0.7](https://github.com/locationtech/spatial4j/releases/tag/spatial4j-0.7) |
|
||||
| [locationtech/jts](https://github.com/locationtech/jts) | 1.15.0 | [jts-1.15.0](https://github.com/locationtech/jts/releases/tag/jts-1.15.0) |
|
||||
| [apache/logging-log4j2](https://github.com/apache/logging-log4j2) | 2.11 | [log4j-2.11.0](https://github.com/apache/logging-log4j2/releases/tag/log4j-2.11.0) |
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About your profile](/articles/about-your-profile)"
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
title: Anheften von Elementen an dein Profil
|
||||
intro: 'Du kannst Gists und Repositorys an dein Profil anheften, damit andere Personen dein beste Arbeit schnell sehen können.'
|
||||
redirect_from:
|
||||
- /articles/pinning-repositories-to-your-profile
|
||||
- /articles/pinning-items-to-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
shortTitle: Pin items
|
||||
ms.openlocfilehash: 131bdb1ed57383e0b420308a96742a573dd9aa14
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145068967'
|
||||
---
|
||||
Du kannst ein öffentliches Repository anheften, wenn Dir das Repository gehört oder wenn du Beiträge zu dem Repository geleistet hast. Commits zu Forks zählen nicht als Beiträge. Daher kannst du Forks, die du nicht besitzt, auch nicht anheften. Weitere Informationen findest du unter [Warum werden meine Beiträge nicht auf meinem Profil angezeigt?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)
|
||||
|
||||
Du kannst alle öffentlichen Gists anheften, die du besitzt.
|
||||
|
||||
Angeheftete Elemente enthalten wichtige Informationen über das Element, wie beispielsweise die Anzahl der Sterne, die ein Repository erhalten hat, oder die ersten Zeilen eines Gist. Wenn du Elemente an dein Profil angeheftet hast, ersetzt der Bereich „Pinned“ (Angeheftet) den Bereich „Popular repositories“ (Beliebte Repositorys) in deinem Profil.
|
||||
|
||||
Du kannst die Elemente im Bereich „Pinned“ (Angeheftet) neu anordnen. Klicke in der rechten oberen Ecke eines angehefteten Elements auf {% octicon "grabber" aria-label="The grabber symbol" %}, und ziehe es an eine andere Stelle.
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
2. Klicke im Bereich „Beliebte Repositorys“ oder „Angeheftet“ auf **Angeheftete Elemente anpassen**.
|
||||
|
||||
3. Um eine durchsuchbare Liste mit anzuheftenden Elementen anzuzeigen, wähle „Repositories“ (Repositorys), „Gists“ (Gists) oder beides aus.
|
||||
|
||||
4. Um ein bestimmtes Element leichter zu finden, kannst du optional den Namen eines Benutzers, einer Organisation, eines Repositorys oder eines Gists eingeben.
|
||||
|
||||
5. Wähle eine Kombination von bis zu sechs Repositorys und/oder Gists zum Anzeigen aus.
|
||||
|
||||
6. Klicke auf **Angeheftete Elemente speichern**.
|
||||
|
||||
|
||||
## Weitere Informationsquellen
|
||||
|
||||
- [Informationen zu deinem Profil](/articles/about-your-profile)
|
||||
@@ -0,0 +1,62 @@
|
||||
---
|
||||
title: Festlegen deines Profils auf privat
|
||||
intro: Ein privates Profil zeigt nur eingeschränkte Informationen an und blendet einige Aktivitäten aus.
|
||||
versions:
|
||||
fpt: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
shortTitle: Set profile to private
|
||||
ms.openlocfilehash: c00718c84d99de95a9ca1352f32954279906451d
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148008151'
|
||||
---
|
||||
## Informationen zu privaten Profilen
|
||||
|
||||
Um Teile deiner Profilseite auszublenden, kannst du dein Profil auf privat setzen. Dadurch wird auch deine Aktivität bei verschiedenen sozialen Features auf {% data variables.product.prodname_dotcom_the_website %} ausgeblendet. Bei einem privaten Profil werden alle Informationen für Benutzer*innen ausgeblendet. Aktuell gibt es keine Option, mit der nur bestimmte Benutzer*innen deine Aktivität sehen können.
|
||||
|
||||
Nachdem du dein Profil auf privat gesetzt hast, kannst du weiterhin alle deine Informationen anzeigen, wenn du dein eigenes Profil besuchst.
|
||||
|
||||
Private Profile können keine Sponsoren unter [{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors) erhalten. Um für {% data variables.product.prodname_sponsors %} zu sein, darf dein Profil nicht auf privat gesetzt sein.
|
||||
|
||||
## Unterschiede zwischen privaten und öffentlichen Profilen
|
||||
|
||||
Wenn dein Profil auf privat gesetzt ist, wird der folgende Inhalt auf deiner Profilseite ausgeblendet:
|
||||
|
||||
- Erfolge und Highlights
|
||||
- Aktivitätsübersicht und Aktivitätsfeed
|
||||
- Beitragsdiagramm
|
||||
- Anzahl der Follower und der Personen, denen du folgst
|
||||
- Schaltflächen „Folgen“ und „Sponsern“
|
||||
- Organisationsmitgliedschaften
|
||||
- Sterne, Projekte, Pakete und Sponsorenregisterkarten
|
||||
|
||||
{% note %}
|
||||
|
||||
**Hinweis**: Wenn dein Profil auf privat gesetzt ist, sind einige optionale Felder immer noch öffentlich sichtbar, z. B. die README-Datei, die Biografie und das Profilfoto.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Änderungen an der Berichterstattung über deine Aktivitäten
|
||||
|
||||
Indem du dein Profil auf privat setzt, entfernst du die vergangenen Aktivitäten nicht und blendest sie nicht aus. Diese Einstellung gilt nur für deine Aktivitäten, während die private Einstellung aktiviert ist.
|
||||
|
||||
Wenn dein Profil auf privat gesetzt ist, ist deine Aktivität auf {% data variables.product.prodname_dotcom_the_website %} an folgenden Orten nicht sichtbar:
|
||||
|
||||
- Aktivitätsfeeds für andere Benutzer*innen
|
||||
- Diskussionsleaderboards
|
||||
- Auf der Seite [Trending](https://github.com/trending)
|
||||
|
||||
{% note %}
|
||||
|
||||
**Hinweis**: Deine Aktivität in öffentlichen Repositorys ist immer noch für alle, die diese Repositorys aufrufen, öffentlich sichtbar, und manche Aktivitätsdaten können noch über die {% data variables.product.prodname_dotcom %}-API verfügbar sein.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Ändern der Privatsphäreeinstellungen deines Profils
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
1. Wähle unter „Beiträge & Aktivität“ das Kontrollkästchen neben **Profil auf privat setzen und Aktivitäten ausblenden** aus.
|
||||
{% data reusables.user-settings.update-preferences %}
|
||||
@@ -0,0 +1,25 @@
|
||||
---
|
||||
title: Einrichten und Verwalten deines GitHub-Profils
|
||||
intro: Du kannst dein GitHub-Profil anpassen und dein Beitragsdiagramm verwalten.
|
||||
shortTitle: Profiles
|
||||
redirect_from:
|
||||
- /categories/setting-up-and-managing-your-github-profile
|
||||
- /github/setting-up-and-managing-your-github-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
children:
|
||||
- /customizing-your-profile
|
||||
- /managing-contribution-settings-on-your-profile
|
||||
ms.openlocfilehash: 3901682d8723e2bdbe2351b7e1f39ccb34971cac
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146199922'
|
||||
---
|
||||
|
||||
@@ -0,0 +1,30 @@
|
||||
---
|
||||
title: Verwalten von Beitragseinstellungen in deinem Profil
|
||||
intro: 'Deine Beiträge, darunter Commits, vorgeschlagene Pull Requests und geöffnete Issues, werden in deinem Profil angezeigt, damit andere Personen deine Arbeit leicht finden können.'
|
||||
redirect_from:
|
||||
- /articles/managing-contribution-graphs-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
children:
|
||||
- /viewing-contributions-on-your-profile
|
||||
- /showing-an-overview-of-your-activity-on-your-profile
|
||||
- /showing-your-private-contributions-and-achievements-on-your-profile
|
||||
- /sending-enterprise-contributions-to-your-githubcom-profile
|
||||
- /why-are-my-contributions-not-showing-up-on-my-profile
|
||||
- /troubleshooting-commits-on-your-timeline
|
||||
shortTitle: Manage contribution settings
|
||||
ms.openlocfilehash: 022a9afdb91a5c65cea12c4bbeef5c4ba9673be6
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '147881211'
|
||||
---
|
||||
|
||||
@@ -0,0 +1,64 @@
|
||||
---
|
||||
title: Senden von Unternehmensbeiträgen an dein GitHub.com-Profil
|
||||
intro: 'Du kannst deine Arbeiten auf {% data variables.product.prodname_enterprise %} hervorheben, indem du die Anzahl deiner Beiträge an dein {% data variables.product.prodname_dotcom_the_website %}-Profil sendest.'
|
||||
redirect_from:
|
||||
- /articles/sending-your-github-enterprise-contributions-to-your-github-com-profile
|
||||
- /articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile
|
||||
- /articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
shortTitle: Send enterprise contributions
|
||||
ms.openlocfilehash: 6fb1803f3a93dd03af24ce9ea3f360e579d7dbd1
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '147079944'
|
||||
---
|
||||
## Informationen zu Unternehmensbeiträgen zu deinem {% data variables.product.prodname_dotcom_the_website %}-Profil
|
||||
|
||||
In deinem {% data variables.product.prodname_dotcom_the_website %}-Profil wird die Anzahl der {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %}-Beiträge der letzten 90 Tage angezeigt. Die {% data reusables.github-connect.sync-frequency %}-Beiträge von {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} gelten als private Beiträge. Die Commitdetails enthalten nur die Beitragsanzahl und dass diese Beiträge in einer {% data variables.product.prodname_enterprise %}-Umgebung außerhalb von {% data variables.product.prodname_dotcom_the_website %} vorgenommen wurden.
|
||||
|
||||
Du entscheidest, ob die Anzahl privater Beiträge auf deinem Profil angezeigt werden soll. Weitere Informationen findest du unter [Veröffentlichen oder Ausblenden deiner privaten Beiträge in deinem Profil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile/).
|
||||
|
||||
Weitere Informationen dazu, wie Beiträge berechnet werden, findest du unter [Verwalten von Beitragsdiagrammen auf deinem Profil](/articles/managing-contribution-graphs-on-your-profile/).
|
||||
|
||||
{% note %}
|
||||
|
||||
**Hinweise:**
|
||||
- Die Verbindungen zwischen deinen Konten werden durch die [Datenschutzbestimmungen von GitHub](/free-pro-team@latest/github/site-policy/github-privacy-statement/) geregelt, und Benutzer*innen, die solche Verbindungen erlauben, sind mit den [Nutzungsbedingungen von GitHub](/free-pro-team@latest/github/site-policy/github-terms-of-service) einverstanden.
|
||||
|
||||
- Damit du dein {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %}-Profil mit deinem {% data variables.product.prodname_dotcom_the_website %}-Profil verbinden kannst, muss der Unternehmensbesitzer {% data variables.product.prodname_github_connect %} aktivieren und die Beitragsfreigabe zwischen den Umgebungen aktivieren. Für weitere Informationen hierzu wendest du dich an deinen Unternehmensbesitzer.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Senden von Unternehmensbeiträgen zu deinem {% data variables.product.prodname_dotcom_the_website %}-Profil
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
- Informationen zum Senden von Unternehmensbeiträgen von {% data variables.product.prodname_ghe_server %} an dein {% data variables.product.prodname_dotcom_the_website %}-Profil findest du unter [Senden von Unternehmensbeiträgen an dein {% data variables.product.prodname_dotcom_the_website %}-Profil](/enterprise-server/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile) in der Dokumentation zu {% data variables.product.prodname_ghe_server %}.
|
||||
- Informationen zum Senden von Unternehmensbeiträgen von {% data variables.product.prodname_ghe_managed %} an dein {% data variables.product.prodname_dotcom_the_website %}-Profil findest du unter [Senden von Unternehmensbeiträgen an dein {% data variables.product.prodname_dotcom_the_website %}-Profil](/github-ae@latest/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile) in der Dokumentation zu {% data variables.product.prodname_ghe_managed %}.
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
1. Melde dich bei {% data variables.product.prodname_ghe_server %} und {% data variables.product.prodname_dotcom_the_website %} an.
|
||||
1. Klicke rechts oben auf einer {% data variables.product.prodname_ghe_server %}-Seite auf dein Profilfoto und dann auf **Einstellungen**.
|
||||
 {% data reusables.github-connect.github-connect-tab-user-settings %} {% data reusables.github-connect.connect-dotcom-and-enterprise %}
|
||||
1. Überprüfe die Ressourcen, auf die {% data variables.product.prodname_ghe_server %} von deinem {% data variables.product.prodname_dotcom_the_website %}-Konto zugreifen wird, und klicke dann auf **Autorisieren**.
|
||||
 {% data reusables.github-connect.send-contribution-counts-to-githubcom %}
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
1. Melde dich bei {% data variables.product.prodname_ghe_managed %} und {% data variables.product.prodname_dotcom_the_website %} an.
|
||||
1. Klicke rechts oben auf einer {% data variables.product.prodname_ghe_managed %}-Seite auf dein Profilfoto und dann auf **Einstellungen**.
|
||||
 {% data reusables.github-connect.github-connect-tab-user-settings %} {% data reusables.github-connect.connect-dotcom-and-enterprise %} {% data reusables.github-connect.authorize-connection %} {% data reusables.github-connect.send-contribution-counts-to-githubcom %}
|
||||
|
||||
{% endif %}
|
||||
@@ -0,0 +1,30 @@
|
||||
---
|
||||
title: Übersicht über Ihre Aktivitäten in Ihrem Profil anzeigen
|
||||
intro: 'In deinem Profil kannst du die Aktivitätsübersicht aktivieren, in der Betrachter eine Übersicht über die Art deiner Beiträge erhalten.'
|
||||
redirect_from:
|
||||
- /articles/showing-an-overview-of-your-activity-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
shortTitle: Show an overview
|
||||
ms.openlocfilehash: a706c476cad8a2474ff1971dc8d81e680cf5c5c3
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147079955'
|
||||
---
|
||||
{% data reusables.profile.activity-overview-summary %} Weitere Informationen findest Du unter "[Anzeigen von Beiträgen auf Deinem Profil](/articles/viewing-contributions-on-your-profile)."
|
||||
|
||||
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
2. Verwende über Deinem Beitragsdiagramm das Dropdownmenü **Contribution settings** (Beitragseinstellungen), und aktiviere oder deaktiviere die Auswahl **Activity overview** (Aktivitätsübersicht).
|
||||
|
||||
@@ -0,0 +1,55 @@
|
||||
---
|
||||
title: Showing your private contributions and achievements on your profile
|
||||
intro: 'Your {% data variables.product.product_name %} profile shows a graph of your repository contributions over the past year. You can choose to show anonymized activity from {% ifversion fpt or ghes or ghec %}private and internal{% else %}private{% endif %} repositories{% ifversion fpt or ghes or ghec %} in addition to the activity from public repositories{% endif %}.'
|
||||
redirect_from:
|
||||
- /articles/publicizing-or-hiding-your-private-contributions-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
shortTitle: Private contributions and achievements
|
||||
---
|
||||
|
||||
If you publicize your private contributions, people without access to the private repositories you work in won't be able to see the details of your private contributions. Instead, they'll see the number of private contributions you made on any given day. Your public contributions will include detailed information. For more information, see "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% ifversion fpt or ghes or ghec %}On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, public contributions on your profile are visible {% ifversion fpt or ghec %}to anyone in the world who can access {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}only to other users of {% data variables.location.product_location%}{% endif %}.{% elsif ghae %}On {% data variables.product.prodname_ghe_managed %}, only other members of your enterprise can see the contributions on your profile.{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Changing the visibility of your private contributions
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
1. Publicize or hide your private contributions on your profile:
|
||||
- To publicize your private contributions, above your contributions graph, use the **Contribution settings** drop-down menu, and select **Private contributions**. Visitors will see your private contribution counts without further details.
|
||||
|
||||
- To hide your private contributions, above your contributions graph, use the **Contribution settings** drop-down menu, and unselect **Private contributions.** Visitors will only see your public contributions.
|
||||
|
||||
|
||||
## Changing the visibility of Achievements
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
1. Show or hide Achievements on your profile:
|
||||
- To show Achievements on your profile, navigate to **Profile settings**, and select the checkbox next to **Show Achievements on my profile.**
|
||||
|
||||
- To hide Achievements from your profile, navigate to **Profile settings**, and unselect the checkbox next to **Show Achievements on my profile.**
|
||||
|
||||
{% ifversion hide-individual-achievements %}
|
||||
1. Optionally, to hide individual Achievements from your profile:
|
||||
{% data reusables.profile.access_profile %}
|
||||
1. Navigate to the Achievements section on the left sidebar of your profile and select the Achievements header. 
|
||||
2. Open the detail view of the achievement you'd like to hide by clicking on the achievement.
|
||||
3. Once in the detail view, click the {% octicon "eye" aria-label="The eye icon" %} icon to hide the achievement.  When hidden, badges will be marked by the {% octicon "eye-closed" aria-label="The eye closed icon" %} icon and are only visible to you. 
|
||||
|
||||
{% endif %}
|
||||
## Further reading
|
||||
|
||||
- "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)"
|
||||
- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"
|
||||
@@ -0,0 +1,75 @@
|
||||
---
|
||||
title: Fehlerbehebung bei Commits auf Ihrer Zeitleiste
|
||||
intro: 'Details zu einzelnen Commits findest Du in der Zeitleiste Deines Profils. Wenn Du in Deinem Profil respektive auf der Profilseite keine Details zu einem erwarteten Commit findest, weichen das Erstellungs- und das Commit-Datum des Commits eventuell voneinander ab.'
|
||||
redirect_from:
|
||||
- /articles/troubleshooting-commits-on-your-timeline
|
||||
- /github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
shortTitle: Troubleshoot commits
|
||||
ms.openlocfilehash: 2a1c89fa158f562bc93e1c76489a077a43e410c3
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147079914'
|
||||
---
|
||||
## Erwartetes Verhalten bei der Anzeige der Commit-Details über die Zeitleiste
|
||||
|
||||
Wenn Du in der Zeitleiste Deiner Profilseite neben einem Repository auf die Anzahl der Commits klickst, werden die Details zu Deinen Commits des betreffenden Zeitraums angezeigt, einschließlich eines Diffs der spezifischen Änderungen am Repository.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Fehlende Commit-Details in der Zeitleiste
|
||||
|
||||
Wenn Du auf Deiner Profilseite auf einen Commit-Link klickst und auf der Commit-Seite des Repositorys nicht alle erwarteten Commits vorfindest, könnte es sein, dass der Commit-Verlauf in Git umgeschrieben wurde und das Erstellungs- und das Commit-Datum der Commits voneinander abweichen.
|
||||
|
||||
|
||||
|
||||
## So verwendet GitHub das Erstellungs- und Commit-Datum von Git
|
||||
|
||||
In Git bezeichnet das Erstellungsdatum das Datum, an dem ein Commit ursprünglich mit dem Befehl `git commit` erstellt wurde. Das Commit-Datum ist mit diesem Datum identisch, solange der ursprüngliche Commit, und damit das Commit-Datum, nicht später durch `git commit --amend`, einen erzwungenen Push, ein Rebase oder einen anderen Git-Befehl geändert wurde.
|
||||
|
||||
Auf Deiner Profilseite wird das Bearbeitungsdatum zur Berechnung des Commit-Datums verwendet. In einem Repository gilt dagegen das Commit-Datum als Erstellungsdatum des Commits im Repository.
|
||||
|
||||
Meist sind das Verfassungs- und Commit-Datum identisch. Gelegentlich aber gerät die Commit-Abfolge durcheinander, wenn der Commit-Verlauf geändert wird. Weitere Informationen findest du unter [Warum werden meine Beiträge nicht auf meinem Profil angezeigt?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)
|
||||
|
||||
## Fehlende Commit-Details in der Zeitleiste anzeigen
|
||||
|
||||
Du kannst den `git show`-Befehl mit dem `--pretty=fuller`-Flag verwenden, um zu überprüfen, ob das Commit-Erstellungsdatum und das Commit-Datum unterschiedlich sind.
|
||||
|
||||
```shell
|
||||
$ git show <em>Your commit SHA number</em> --pretty=fuller
|
||||
commit <em>Your commit SHA number</em>
|
||||
Author: octocat <em>user email</em>
|
||||
AuthorDate: Tue Apr 03 02:02:30 2018 +0900
|
||||
Commit: Sally Johnson <em>user email</em>
|
||||
CommitDate: Tue Apr 10 06:25:08 2018 +0900
|
||||
```
|
||||
|
||||
Weichen das Erstellungs- und Commit-Datum voneinander ab, kannst Du das Commit-Datum in der URL manuell ändern, um die Commit-Details anzuzeigen.
|
||||
|
||||
Zum Beispiel:
|
||||
- Die folgende URL verwendet das Erstellungsdatum `2018-04-03`:
|
||||
|
||||
`https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-03T00:00:00Z&until=2018-04-03T23:59:59Z`
|
||||
- Die folgende URL verwendet das Commit-Datum `2018-04-10`:
|
||||
|
||||
`https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-10T00:00:00Z&until=2018-04-10T23:59:59Z`
|
||||
|
||||
Wenn Du die URL mit dem korrigierten Commit-Datum aufrufst, werden die Commit-Details angezeigt.
|
||||
|
||||
|
||||
|
||||
## Wenn erwartete Commits in der Zeitleiste fehlen
|
||||
|
||||
Wenn in Deiner Zeitleiste nicht alle erwarteten Commits angezeigt werden, könnte es sein, dass der Commit-Verlauf in Git umgeschrieben wurde und das Erstellungs- und das Commit-Datum der Commits voneinander abweichen. Andere Möglichkeiten findest du unter [Warum werden meine Beiträge nicht auf meinem Profil angezeigt?](/articles/why-are-my-contributions-not-showing-up-on-my-profile).
|
||||
@@ -0,0 +1,97 @@
|
||||
---
|
||||
title: Viewing contributions on your profile
|
||||
intro: 'Your {% data variables.product.product_name %} profile shows off {% ifversion fpt or ghes or ghec %}your pinned repositories, Achievements, and{% endif %} a graph of your repository contributions over the past year.'
|
||||
redirect_from:
|
||||
- /articles/viewing-contributions
|
||||
- /articles/viewing-contributions-on-your-profile-page
|
||||
- /articles/viewing-contributions-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
shortTitle: View contributions
|
||||
---
|
||||
{% ifversion fpt or ghes or ghec %}Your contribution graph and Achievements show activity from public repositories. {% endif %}You can choose to show activity from {% ifversion fpt or ghes or ghec %}both public and {% endif %}private repositories, with specific details of your activity in private repositories anonymized. For more information, see "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Commits will only appear on your contributions graph if the email address you used to author the commits is connected to your account on {% data variables.product.product_name %}. For more information, see "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)"
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## What counts as a contribution
|
||||
|
||||
On your profile page, certain actions count as contributions:
|
||||
|
||||
- Committing to a repository's default branch or `gh-pages` branch
|
||||
- Opening an issue
|
||||
- Opening a discussion
|
||||
- Answering a discussion
|
||||
- Proposing a pull request
|
||||
- Submitting a pull request review{% ifversion ghes or ghae %}
|
||||
- Co-authoring commits in a repository's default branch or `gh-pages` branch{% endif %}
|
||||
|
||||
{% data reusables.pull_requests.pull_request_merges_and_contributions %}
|
||||
|
||||
## Popular repositories
|
||||
|
||||
This section displays your repositories with the most watchers. {% ifversion fpt or ghes or ghec %}Once you [pin repositories to your profile](/articles/pinning-repositories-to-your-profile), this section will change to "Pinned repositories."{% endif %}
|
||||
|
||||
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
## Pinned repositories
|
||||
|
||||
This section displays up to six public repositories and can include your repositories as well as repositories you've contributed to. To easily see important details about the repositories you've chosen to feature, each repository in this section includes a summary of the work being done, the number of [stars](/articles/saving-repositories-with-stars/) the repository has received, and the main programming language used in the repository. For more information, see "[Pinning repositories to your profile](/articles/pinning-repositories-to-your-profile)."
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Contributions calendar
|
||||
|
||||
Your contributions calendar shows your contribution activity.
|
||||
|
||||
### Viewing contributions from specific times
|
||||
|
||||
- Click on a day's square to show the contributions made during that 24-hour period.
|
||||
- Press *Shift* and click on another day's square to show contributions made during that time span.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You can select up to a one-month range on your contributions calendar. If you select a larger time span, we will only display one month of contributions.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
|
||||
### How contribution event times are calculated
|
||||
|
||||
Timestamps are calculated differently for commits and pull requests:
|
||||
- **Commits** use the time zone information in the commit timestamp. For more information, see "[Troubleshooting commits on your timeline](/articles/troubleshooting-commits-on-your-timeline)."
|
||||
- **Pull requests** and **issues** opened on {% data variables.product.product_name %} use your browser's time zone. Those opened via the API use the timestamp or time zone [specified in the API call](https://developer.github.com/changes/2014-03-04-timezone-handling-changes).
|
||||
|
||||
## Activity overview
|
||||
|
||||
{% data reusables.profile.activity-overview-summary %} For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)."
|
||||
|
||||
|
||||
|
||||
The organizations featured in the activity overview are prioritized according to how active you are in the organization. If you @mention an organization in your profile bio, and you’re an organization member, then that organization is prioritized first in the activity overview. For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)" or "[Adding a bio to your profile](/articles/adding-a-bio-to-your-profile/)."
|
||||
|
||||
## Contribution activity
|
||||
|
||||
The contribution activity section includes a detailed timeline of your work, including commits you've made or co-authored, pull requests you've proposed, and issues you've opened. You can see your contributions over time by either clicking **Show more activity** at the bottom of your contribution activity or by clicking the year you're interested in viewing on the right side of the page. Important moments, like the date you joined an organization, proposed your first pull request, or opened a high-profile issue, are highlighted in your contribution activity. If you can't see certain events in your timeline, check to make sure you still have access to the organization or repository where the event happened.
|
||||
|
||||
|
||||
|
||||
## Viewing contributions from {% data variables.product.prodname_enterprise %} on {% data variables.product.prodname_dotcom_the_website %}
|
||||
|
||||
If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and your enterprise owner enables {% data variables.enterprise.prodname_unified_contributions %}, you can send enterprise contribution counts from to your {% data variables.product.prodname_dotcom_the_website %} profile. For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)."
|
||||
|
||||
@@ -0,0 +1,108 @@
|
||||
---
|
||||
title: Warum werden meine Beiträge nicht in meinem Profil angezeigt?
|
||||
intro: 'Hier lernst du häufige Gründe kennen, aus denen Beiträge in deinem Beitragsdiagramm fehlen.'
|
||||
redirect_from:
|
||||
- /articles/why-are-my-contributions-not-showing-up-on-my-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
shortTitle: Missing contributions
|
||||
ms.openlocfilehash: f3480b1b4f2857a144ad8e264e0d8b78196b1a3e
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107045'
|
||||
---
|
||||
## Informationen zu deinem Beitragsdiagramm
|
||||
|
||||
Dein Profilbeitragsdiagramm ist eine Aufzeichnung deiner Beiträge zu Repositorys {% ifversion ghae %}im Besitz von {% else %}auf{% endif %} {% data variables.location.product_location %}. Beiträge werden nicht entsprechend deiner lokalen Zeitzone, sondern entsprechend der UTC-Zone (Coordinated Universal Time, koordinierte Weltzeit) mit Zeitstempeln versehen. Beiträge werden nur gezählt, falls sie bestimmte Kriterien erfüllen. In manchen Fällen muss dein Diagramm allenfalls neu erstellt werden, damit die Beiträge angezeigt werden.
|
||||
|
||||
Wenn du einer Organisation angehörst, die einmaliges Anmelden (Single Sign-On, SSO) mit SAML verwendet, werden dir in deinem Profil keine Beitragsaktivitäten aus der Organisation angezeigt, wenn du über keine aktive SSO-Sitzung verfügst. Personen, die sich dein Profil außerhalb deiner Organisation ansehen, werden anonymisierte Beitragsaktivitäten für deine Organisation angezeigt.
|
||||
|
||||
## Gezählte Beiträge
|
||||
|
||||
### Issues, Pull Requests und Diskussionen
|
||||
|
||||
Issues, Pull Requests und Diskussionen werden in deinem Beteiligungsdiagramm angezeigt, sofern sie in einem eigenständigen Repository und nicht in einem Fork geöffnet wurden.
|
||||
|
||||
### Commits
|
||||
Commits werden in deinem Beteiligungsdiagramm angezeigt, sofern sie **alle** folgenden Bedingungen erfüllen:
|
||||
- Die für die Commits verwendete E-Mail-Adresse ist deinem Konto auf {% data variables.location.product_location %} zugeordnet.
|
||||
- Die Commits wurden in einem eigenständigen Repository vorgenommen und nicht in einem Fork.
|
||||
- Die Commits wurden
|
||||
- im Standardbranch des Repositorys vorgenommen.
|
||||
- im Branch `gh-pages` vorgenommen (für Repositorys mit Projektwebsites).
|
||||
|
||||
Weitere Informationen zu Projektwebsites findest du unter [Informationen zu {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites).
|
||||
|
||||
Darüber hinaus muss **mindestens eine** der folgenden Bedingungen erfüllt sein:
|
||||
- Du bist ein Repository-Mitarbeiter oder ein Mitglied der Organisation, welcher das Repository gehört.
|
||||
- Du hast das Repository geforkt.
|
||||
- Du hast einen Pull Request oder Issue im Repository geöffnet.
|
||||
- Du hast das Repository mit Sternen versehen.
|
||||
|
||||
## Allgemeine Ursachen für nicht gezählte Beiträge
|
||||
|
||||
{% data reusables.pull_requests.pull_request_merges_and_contributions %}
|
||||
|
||||
### Die Commit-Erstellung liegt weniger als 24 Stunden zurück
|
||||
|
||||
Nachdem du einen Commit erstellt hast, der die Anforderung erfüllt, um als Beitrag gezählt zu werden, kann es bis zu 24 Stunden dauern, bis der Beitrag in deinem Beteiligungsdiagramm angezeigt wird.
|
||||
|
||||
### Deine lokale Git-Commit-E-Mail-Adresse ist nicht mit deinem Konto verknüpft.
|
||||
|
||||
Damit Commits in deinem Beitragsdiagramm angezeigt werden, müssen sie mit einer E-Mail-Adresse vorgenommen werden, die mit deinem Konto auf {% data variables.location.product_location %} verknüpft ist{% ifversion fpt or ghec %}, oder unter Verwendung der von {% data variables.product.prodname_dotcom %} angegebenen `noreply`-E-Mail-Adresse aus deinen E-Mail-Einstellungen{% endif %}.{% ifversion fpt or ghec %} Weitere Informationen zu `noreply`-E-Mail-Adressen findest du unter [Festlegen der E-Mail-Adresse für Commits](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#about-commit-email-addresses).{% endif %}
|
||||
|
||||
Du kannst die für einen Commit verwendete E-Mail-Adresse überprüfen, indem du `.patch` ans Ende einer Commit-URL anhängst, z. B. <a href="https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch" data-proofer-ignore>https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch</a>:
|
||||
|
||||
```
|
||||
From 67c0afc1da354d8571f51b6f0af8f2794117fd10 Mon Sep 17 00:00:00 2001
|
||||
From: The Octocat <octocat@nowhere.com>
|
||||
Date: Sun, 27 Apr 2014 15:36:39 +0530
|
||||
Subject: [PATCH] updated index for better welcome message
|
||||
```
|
||||
|
||||
Die E-Mail-Adresse im Feld `From:` ist die Adresse, die in den [Einstellungen für die lokale Git-Konfiguration](/articles/set-up-git) festgelegt wurde. In diesem Beispiel wurde für den Commit die E-Mail-Adresse `octocat@nowhere.com` verwendet.
|
||||
|
||||
Wenn die für den Commit verwendete E-Mail-Adresse nicht mit deinem Konto auf {% data variables.location.product_location %} verknüpft ist, {% ifversion ghae %}ändere die E-Mail-Adresse, die beim Erstellen von Commits in Git verwendet wird. Weitere Informationen findest du unter [E-Mail-Adresse für Commits festlegen](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git).{% else %}musst du deinem Konto auf {% data variables.location.product_location %} [die E-Mail-Adresse hinzufügen](/articles/adding-an-email-address-to-your-github-account). Beim Hinzufügen der neuen Adresse wird dein Beteiligungsdiagramm automatisch neu erstellt.{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %} {% note %}
|
||||
|
||||
**Hinweis**: Wenn du einen {% data variables.enterprise.prodname_managed_user %} verwendest, kannst du dem Konto keine weiteren E-Mail-Adressen hinzufügen. Dies gilt selbst dann, wenn mehrere E-Mail-Adressen bei deinem Identitätsanbieter (IdP) registriert sind. Daher können deinem {% data variables.enterprise.prodname_managed_user %} nur Commits zugeordnet werden, die über die primäre E-Mail-Adresse erstellt wurden, die bei deinem IdP registriert ist.
|
||||
|
||||
{% endnote %} {% endif %}
|
||||
|
||||
Generische E-Mail-Adressen (beispielsweise `jane@computer.local`) können nicht zu {% data variables.product.prodname_dotcom %}-Konten hinzugefügt und mit Commits verknüpft werden. Wenn du Commits mit einer generischen E-Mail-Adresse erstellt hast, werden die Commits nicht mit deinem {% data variables.product.prodname_dotcom %}-Profil verknüpft und erscheinen nicht in deinem Beitragsdiagramm.
|
||||
|
||||
### Der Commit wurde weder im Standardbranch noch im Branch `gh-pages` vorgenommen.
|
||||
|
||||
Commits werden nur berücksichtigt, wenn sie im Standardbranch oder im Branch `gh-pages` (für Repositorys mit Projektwebsites) vorgenommen wurden. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites).
|
||||
|
||||
Falls deine Commits in einem Branch vorgenommen wurden, bei dem es sich nicht um den Standardbranch und nicht um den Branch `gh-pages` handelt, und die Commits in deinen Beiträgen berücksichtigt werden sollen, ist eine der folgenden Aktionen erforderlich:
|
||||
- [Erstelle einen Pull Request](/articles/creating-a-pull-request), damit deine Änderungen mit dem Standardbranch oder mit dem Branch `gh-pages` zusammengeführt werden.
|
||||
- [Ändere den Standardbranch](/github/administering-a-repository/changing-the-default-branch) des Repositorys.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warnung:** Wenn du den Standardbranch des Repositorys änderst, wird er für alle Repository-Mitarbeiter geändert. Führe diese Aktion nur dann aus, wenn du willst, dass der neue Branch zur neuen Basis wird, auf der alle künftigen Pull Requests und Commits durchgeführt werden.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
### Commit wurde in einem Fork durchgeführt
|
||||
|
||||
Die in einem Fork durchgeführten Commits werden nicht auf deine Beiträge angerechnet. Führe eine der folgenden Aktionen durch, damit sie angerechnet werden:
|
||||
- [Erstelle einen Pull Request](/articles/creating-a-pull-request), damit deine Änderungen mit dem übergeordneten Repository zusammengeführt werden.
|
||||
- Falls du den Fork abtrennen und in ein eigenständiges Repository auf {% data variables.location.product_location %} umwandeln möchtest, wende dich an den {% data variables.contact.contact_support %}. Wenn der Fork über eigene Forks verfügt, musst du {% data variables.contact.contact_support %} mitteilen, ob die Forks zusammen mit deinem Repository in ein neues Netzwerk verschoben werden oder im aktuellen Netzwerk verbleiben sollen. Weitere Informationen findest du unter [Informationen zu Forks](/articles/about-forks/).
|
||||
|
||||
## Weitere Informationsquellen
|
||||
|
||||
- [Private Beiträge in deinem Profil veröffentlichen oder verbergen](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)
|
||||
- [Beiträge auf deiner Profilseite anzeigen](/articles/viewing-contributions-on-your-profile-page)
|
||||
@@ -0,0 +1,29 @@
|
||||
---
|
||||
title: Einrichten und Verwalten deines persönlichen Kontos auf GitHub
|
||||
intro: 'Du kannst die Einstellungen für dein persönliches Konto auf {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} verwalten, einschließlich E-Mail-Einstellungen, Zugang zu persönlichen Repositorys und Organisationsmitgliedschaften. Du kannst das Konto auch selbst verwalten.'
|
||||
shortTitle: Personal accounts
|
||||
redirect_from:
|
||||
- /categories/setting-up-and-managing-your-github-user-account
|
||||
- /github/setting-up-and-managing-your-github-user-account
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
children:
|
||||
- /managing-personal-account-settings
|
||||
- /managing-your-personal-account
|
||||
- /managing-email-preferences
|
||||
- /managing-access-to-your-personal-repositories
|
||||
- /managing-your-membership-in-organizations
|
||||
ms.openlocfilehash: b3c8007f37b9c61650f96a51e805024dd10a853f
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148106685'
|
||||
---
|
||||
|
||||
@@ -0,0 +1,32 @@
|
||||
---
|
||||
title: Zugriff auf Ihre persönlichen Repositorys verwalten
|
||||
intro: Du kannst anderen Personen Zugriff als Mitarbeiter auf Repositorys deines persönlichen Kontos gewähren.
|
||||
redirect_from:
|
||||
- /categories/101/articles
|
||||
- /categories/managing-repository-collaborators
|
||||
- /articles/managing-access-to-your-personal-repositories
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories
|
||||
product: '{% data reusables.gated-features.user-repo-collaborators %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
- Repositories
|
||||
children:
|
||||
- /inviting-collaborators-to-a-personal-repository
|
||||
- /removing-a-collaborator-from-a-personal-repository
|
||||
- /removing-yourself-from-a-collaborators-repository
|
||||
- /maintaining-ownership-continuity-of-your-personal-accounts-repositories
|
||||
shortTitle: Access to your repositories
|
||||
ms.openlocfilehash: 98b504beea02ce0dfb73ebe2db34fea498c75776
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145164927'
|
||||
---
|
||||
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
title: Inviting collaborators to a personal repository
|
||||
intro: 'You can {% ifversion fpt or ghec %}invite users to become{% else %}add users as{% endif %} collaborators to your personal repository.'
|
||||
redirect_from:
|
||||
- /articles/how-do-i-add-a-collaborator
|
||||
- /articles/adding-collaborators-to-a-personal-repository
|
||||
- /articles/inviting-collaborators-to-a-personal-repository
|
||||
- /github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository
|
||||
product: '{% data reusables.gated-features.user-repo-collaborators %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
- Repositories
|
||||
shortTitle: Invite collaborators
|
||||
---
|
||||
Repositories owned by an organization can grant more granular access. For more information, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github)."
|
||||
|
||||
{% data reusables.organizations.org-invite-expiration %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.product.company_short %} limits the number of people who can be invited to a repository within a 24-hour period. If you exceed this limit, either wait 24 hours or create an organization to collaborate with more people.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
1. Ask for the username of the person you're inviting as a collaborator.{% ifversion fpt or ghec %} If they don't have a username yet, they can sign up for {% data variables.product.prodname_dotcom %} For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)".{% endif %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4%}
|
||||
{% data reusables.repositories.click-collaborators-teams %}
|
||||
1. Click **Invite a collaborator**.
|
||||
|
||||
2. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
|
||||
|
||||
3. Click **Add NAME to REPOSITORY**.
|
||||
|
||||
{% else %}
|
||||
5. In the left sidebar, click **Collaborators**.
|
||||
|
||||
6. Under "Collaborators", start typing the collaborator's username.
|
||||
7. Select the collaborator's username from the drop-down menu.
|
||||
|
||||
8. Click **Add collaborator**.
|
||||
|
||||
{% endif %}
|
||||
{% ifversion fpt or ghec %}
|
||||
9. The user will receive an email inviting them to the repository. Once they accept your invitation, they will have collaborator access to your repository.
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Permission levels for a personal account repository](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-personal-account)"
|
||||
- "[Removing a collaborator from a personal repository](/articles/removing-a-collaborator-from-a-personal-repository)"
|
||||
- "[Removing yourself from a collaborator's repository](/articles/removing-yourself-from-a-collaborator-s-repository)"
|
||||
- "[Organizing members into teams](/organizations/organizing-members-into-teams)"
|
||||
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: Maintaining ownership continuity of your personal account's repositories
|
||||
intro: You can invite someone to manage your user owned repositories if you are not able to.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
- Repositories
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories
|
||||
shortTitle: Ownership continuity
|
||||
---
|
||||
## About successors
|
||||
|
||||
We recommend inviting another {% data variables.product.company_short %} user to be your successor, to manage your user owned repositories if you cannot. As a successor, they will have permission to:
|
||||
|
||||
- Archive your public repositories.
|
||||
- Transfer your public repositories to their own user owned account.
|
||||
- Transfer your public repositories to an organization where they can create repositories.
|
||||
|
||||
Successors cannot log into your account.
|
||||
|
||||
An appointed successor can manage your public repositories after presenting a death certificate then waiting for 7 days or presenting an obituary then waiting for 21 days. For more information, see "[{% data variables.product.company_short %} Deceased User Policy](/free-pro-team@latest/github/site-policy/github-deceased-user-policy)."
|
||||
|
||||
To request access to manage repositories as a successor, contact [GitHub Support](https://support.github.com/contact?tags=docs-accounts).
|
||||
|
||||
## Inviting a successor
|
||||
The person you invite to be your successor must have a {% data variables.product.company_short %} account.
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.account_settings %}
|
||||
3. Under "Successor settings", to invite a successor, begin typing a username, full name, or email address, then click their name when it appears.
|
||||
|
||||
4. Click **Add successor**.
|
||||
{% data reusables.user-settings.sudo-mode-popup %}
|
||||
6. The user you've invited will be listed as "Pending" until they agree to become your successor.
|
||||
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
title: Removing a collaborator from a personal repository
|
||||
intro: 'When you remove a collaborator from your project, they lose read/write access to your repository. If the repository is private and the person has created a fork, then that fork is also deleted.'
|
||||
redirect_from:
|
||||
- /articles/how-do-i-remove-a-collaborator
|
||||
- /articles/what-happens-when-i-remove-a-collaborator-from-my-private-repository
|
||||
- /articles/removing-a-collaborator-from-a-private-repository
|
||||
- /articles/deleting-a-private-fork-of-a-private-user-repository
|
||||
- /articles/how-do-i-delete-a-fork-of-my-private-repository
|
||||
- /articles/removing-a-collaborator-from-a-personal-repository
|
||||
- /github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository
|
||||
product: '{% data reusables.gated-features.user-repo-collaborators %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
- Repositories
|
||||
shortTitle: Remove a collaborator
|
||||
---
|
||||
## Deleting forks of private repositories
|
||||
|
||||
While forks of private repositories are deleted when a collaborator is removed, the person will still retain any local clones of your repository.
|
||||
|
||||
## Removing collaborator permissions from a person contributing to a repository
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
|
||||
{% data reusables.repositories.click-collaborators-teams %}
|
||||
4. To the right of the collaborator you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
|
||||
|
||||
{% else %}
|
||||
3. In the left sidebar, click **Collaborators & teams**.
|
||||
|
||||
4. Next to the collaborator you want to remove, click the **X** icon.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Removing organization members from a team](/articles/removing-organization-members-from-a-team)"
|
||||
- "[Removing an outside collaborator from an organization repository](/articles/removing-an-outside-collaborator-from-an-organization-repository)"
|
||||
@@ -0,0 +1,33 @@
|
||||
---
|
||||
title: Removing yourself from a collaborator's repository
|
||||
intro: 'If you no longer want to be a collaborator on someone else''s repository, you can remove yourself.'
|
||||
redirect_from:
|
||||
- /leave-a-collaborative-repo
|
||||
- /leave-a-repo
|
||||
- /articles/removing-yourself-from-a-collaborator-s-repo
|
||||
- /articles/removing-yourself-from-a-collaborator-s-repository
|
||||
- /articles/removing-yourself-from-a-collaborators-repository
|
||||
- /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
- Repositories
|
||||
shortTitle: Remove yourself
|
||||
---
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
|
||||
2. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
|
||||
{% else %}
|
||||
2. In the left sidebar, click **Repositories**.
|
||||
|
||||
{% endif %}
|
||||
3. Next to the repository you want to leave, click **Leave**.
|
||||
|
||||
4. Read the warning carefully, then click "I understand, leave this repository."
|
||||
|
||||
@@ -0,0 +1,37 @@
|
||||
---
|
||||
title: Adding an email address to your GitHub account
|
||||
intro: '{% data variables.product.product_name %} allows you to add as many email addresses to your account as you like. If you set an email address in your local Git configuration, you will need to add it to your account settings in order to connect your commits to your account. For more information about your email address and commits, see "[Setting your commit email address](/articles/setting-your-commit-email-address/)."'
|
||||
redirect_from:
|
||||
- /articles/adding-an-email-address-to-your-github-account
|
||||
- /github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
- Notifications
|
||||
shortTitle: Add an email address
|
||||
---
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Notes**:
|
||||
- {% data reusables.user-settings.no-verification-disposable-emails %}
|
||||
- If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you cannot make changes to your email address on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.emails %}
|
||||
{% data reusables.user-settings.add_and_verify_email %}
|
||||
{% data reusables.user-settings.select_primary_email %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Managing email preferences](/articles/managing-email-preferences/)"
|
||||
@@ -0,0 +1,29 @@
|
||||
---
|
||||
title: Blocking command line pushes that expose your personal email address
|
||||
intro: 'If you''ve chosen to keep your email address private when performing web-based operations, you can also choose to block command line pushes that may expose your personal email address.'
|
||||
redirect_from:
|
||||
- /articles/blocking-command-line-pushes-that-expose-your-personal-email-address
|
||||
- /github/setting-up-and-managing-your-github-user-account/blocking-command-line-pushes-that-expose-your-personal-email-address
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
- Notifications
|
||||
shortTitle: Block push with personal email
|
||||
---
|
||||
When you push commits from the command line, the email address that you've [set in Git](/articles/setting-your-commit-email-address) is associated with your commits. If you enable this setting, each time you push to GitHub, we’ll check the most recent commit. If the author email on that commit is a private email on your GitHub account, we will block the push and warn you about exposing your private email.
|
||||
|
||||
{% data reusables.user-settings.about-commit-email-addresses %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.emails %}
|
||||
{% data reusables.user-settings.keeping_your_email_address_private %}
|
||||
4. To keep your email address private in commits you push from the command line, select **Block command line pushes that expose my email**.
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Setting your commit email address](/articles/setting-your-commit-email-address)"
|
||||
@@ -0,0 +1,33 @@
|
||||
---
|
||||
title: Changing your primary email address
|
||||
intro: You can change the email address associated with your personal account at any time.
|
||||
redirect_from:
|
||||
- /articles/changing-your-primary-email-address
|
||||
- /github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
- Notifications
|
||||
shortTitle: Primary email address
|
||||
---
|
||||
{% note %}
|
||||
|
||||
**Note:** You cannot change your primary email address to an email that is already set to be your backup email address.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.emails %}
|
||||
3. If you'd like to add a new email address to set as your primary email address, under "Add email address", type a new email address and click **Add**.
|
||||
|
||||
4. Under "Primary email address", use the drop-down menu to click the email address you'd like to set as your primary email address, and click **Save**.
|
||||
|
||||
5. To remove the old email address from your account, next to the old email, click {% octicon "trash" aria-label="The trash symbol" %}.
|
||||
{% ifversion fpt or ghec %}
|
||||
6. Verify your new primary email address. Without a verified email address, you won't be able to use all of {% data variables.product.product_name %}'s features. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."
|
||||
{% endif %}
|
||||
@@ -0,0 +1,28 @@
|
||||
---
|
||||
title: Managing email preferences
|
||||
intro: 'You can add or change the email addresses associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. You can also manage emails you receive from {% data variables.product.product_name %}.'
|
||||
redirect_from:
|
||||
- /categories/managing-email-preferences
|
||||
- /articles/managing-email-preferences
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
- Notifications
|
||||
children:
|
||||
- /adding-an-email-address-to-your-github-account
|
||||
- /changing-your-primary-email-address
|
||||
- /setting-a-backup-email-address
|
||||
- /setting-your-commit-email-address
|
||||
- /blocking-command-line-pushes-that-expose-your-personal-email-address
|
||||
- /remembering-your-github-username-or-email
|
||||
- /types-of-emails-github-sends
|
||||
- /managing-marketing-emails-from-github
|
||||
shortTitle: Manage email preferences
|
||||
---
|
||||
|
||||
@@ -0,0 +1,35 @@
|
||||
---
|
||||
title: Managing marketing emails from GitHub
|
||||
intro: 'In addition to notifications and account emails, {% data variables.product.prodname_dotcom %} occasionally sends marketing emails with news and information about our products. If you unsubscribe from existing marketing emails, you won''t be included in future campaigns unless you change your {% data variables.product.prodname_dotcom %} email settings.'
|
||||
redirect_from:
|
||||
- /articles/managing-marketing-emails-from-github
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-marketing-emails-from-github
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
- Notifications
|
||||
shortTitle: Marketing emails
|
||||
---
|
||||
## Unsubscribing from {% data variables.product.prodname_dotcom %} marketing emails
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** If you unsubscribe from all marketing emails and then subscribe to the Explore newsletter, you'll only receive the Explore newsletter, and won't receive other marketing email.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.emails %}
|
||||
3. Under *Email preferences*, select **Only receive account related emails, and those I subscribe to**.
|
||||
|
||||
4. Click **Save email preferences**.
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Types of emails GitHub sends](/articles/types-of-emails-github-sends)"
|
||||
- "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)"
|
||||
@@ -0,0 +1,76 @@
|
||||
---
|
||||
title: Remembering your GitHub username or email
|
||||
intro: 'Are you signing in to {% data variables.location.product_location %} for the first time in a while? If so, welcome back! If you can''t remember the username for your personal account on {% data variables.product.product_name %}, you can try these methods for remembering it.'
|
||||
redirect_from:
|
||||
- /articles/oh-noes-i-ve-forgotten-my-username-email
|
||||
- /articles/oh-noes-i-ve-forgotten-my-username-or-email
|
||||
- /articles/remembering-your-github-username-or-email
|
||||
- /github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
- Notifications
|
||||
shortTitle: Find your username or email
|
||||
---
|
||||
{% mac %}
|
||||
|
||||
## {% data variables.product.prodname_desktop %} users
|
||||
|
||||
1. In the **GitHub Desktop** menu, click **Preferences**.
|
||||
2. In the Preferences window, verify the following:
|
||||
- To view your {% data variables.product.product_name %} username, click **Accounts**.
|
||||
- To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address).
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
## {% data variables.product.prodname_desktop %} users
|
||||
|
||||
1. In the **File** menu, click **Options**.
|
||||
2. In the Options window, verify the following:
|
||||
- To view your {% data variables.product.product_name %} username, click **Accounts**.
|
||||
- To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address).
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
## Finding your username in your `user.name` configuration
|
||||
|
||||
During set up, you may have [set your username in Git](/github/getting-started-with-github/setting-your-username-in-git). If so, you can review the value of this configuration setting:
|
||||
|
||||
```shell
|
||||
$ git config user.name
|
||||
# View the setting
|
||||
YOUR_USERNAME
|
||||
```
|
||||
|
||||
## Finding your username in the URL of remote repositories
|
||||
|
||||
If you have any local copies of personal repositories you have created or forked, you can check the URL of the remote repository.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip**: This method only works if you have an original repository or your own fork of someone else's repository. If you clone someone else's repository, their username will show instead of yours. Similarly, organization repositories will show the name of the organization instead of a particular user in the remote URL.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
```shell
|
||||
$ cd YOUR_REPOSITORY
|
||||
# Change directories to the initialized Git repository
|
||||
$ git remote -v
|
||||
origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (fetch)
|
||||
origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (push)
|
||||
```
|
||||
|
||||
Your user name is what immediately follows the `https://{% data variables.command_line.backticks %}/`.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## Further reading
|
||||
|
||||
- "[Verifying your email address](/articles/verifying-your-email-address)"
|
||||
{% endif %}
|
||||
@@ -0,0 +1,28 @@
|
||||
---
|
||||
title: Setting a backup email address
|
||||
intro: 'Use a backup email address as an additional destination for security-relevant account notifications{% ifversion not ghae %} and to securely reset your password if you can no longer access your primary email address{% endif %}.'
|
||||
redirect_from:
|
||||
- /articles/setting-a-backup-email-address
|
||||
- /github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
- Notifications
|
||||
shortTitle: Set backup email address
|
||||
---
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.emails %}
|
||||
3. Under "Backup email address," select the address you want to set as your backup email address using the drop-down menu.
|
||||
|
||||
4. Click **Save**.
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Managing email preferences](/articles/managing-email-preferences/)"
|
||||
- "[Updating your GitHub access credentials](/articles/updating-your-github-access-credentials/)"
|
||||
@@ -0,0 +1,105 @@
|
||||
---
|
||||
title: Setting your commit email address
|
||||
intro: 'You can set the email address that is used to author commits on {% data variables.location.product_location %} and on your computer.'
|
||||
redirect_from:
|
||||
- /articles/keeping-your-email-address-private
|
||||
- /articles/setting-your-commit-email-address-on-github
|
||||
- /articles/about-commit-email-addresses
|
||||
- /articles/git-email-settings
|
||||
- /articles/setting-your-email-in-git
|
||||
- /articles/set-your-user-name-email-and-github-token
|
||||
- /articles/setting-your-commit-email-address-in-git
|
||||
- /articles/setting-your-commit-email-address
|
||||
- /github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
- Notifications
|
||||
shortTitle: Set commit email address
|
||||
---
|
||||
## About commit email addresses
|
||||
|
||||
{% data variables.product.prodname_dotcom %} uses your commit email address to associate commits with your account on {% data variables.location.product_location %}. You can choose the email address that will be associated with the commits you push from the command line as well as web-based Git operations you make.
|
||||
|
||||
For web-based Git operations, you can set your commit email address on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For commits you push from the command line, you can set your commit email address in Git.
|
||||
|
||||
{% ifversion fpt or ghec %}Any commits you made prior to changing your commit email address are still associated with your previous email address.{% else %}After changing your commit email address on {% data variables.product.product_name %}, the new email address will be visible in all of your future web-based Git operations by default. Any commits you made prior to changing your commit email address are still associated with your previous email address.{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data reusables.user-settings.no-verification-disposable-emails %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}If you'd like to keep your personal email address private, you can use a `noreply` email address from {% data variables.product.product_name %} as your commit email address. To use your `noreply` email address for commits you push from the command line, use that email address when you set your commit email address in Git. To use your `noreply` address for web-based Git operations, set your commit email address on GitHub and choose to **Keep my email address private**.
|
||||
|
||||
You can also choose to block commits you push from the command line that expose your personal email address. For more information, see "[Blocking command line pushes that expose your personal email](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)."{% endif %}
|
||||
|
||||
To ensure that commits are attributed to you and appear in your contributions graph, use an email address that is connected to your account on {% data variables.location.product_location %}{% ifversion fpt or ghec %}, or the `noreply` email address provided to you in your email settings{% endif %}. {% ifversion not ghae %}For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)."{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you created your account on {% data variables.location.product_location %} _after_ July 18, 2017, your `noreply` email address for {% data variables.product.product_name %} is an ID number and your username in the form of <code>ID+USERNAME@users.noreply.github.com</code>. If you created your account on {% data variables.location.product_location %} _prior to_ July 18, 2017, your `noreply` email address from {% data variables.product.product_name %} is <code>USERNAME@users.noreply.github.com</code>. You can get an ID-based `noreply` email address for {% data variables.product.product_name %} by selecting (or deselecting and reselecting) **Keep my email address private** in your email settings.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If you use your `noreply` email address for {% data variables.product.product_name %} to make commits and then [change your username](/articles/changing-your-github-username), those commits will not be associated with your account on {% data variables.location.product_location %}. This does not apply if you're using the ID-based `noreply` address from {% data variables.product.product_name %}. For more information, see "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username)."{% endif %}
|
||||
|
||||
## Setting your commit email address on {% data variables.product.prodname_dotcom %}
|
||||
|
||||
{% data reusables.files.commit-author-email-options %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.emails %}
|
||||
{% data reusables.user-settings.add_and_verify_email %}
|
||||
{% data reusables.user-settings.select_primary_email %}{% ifversion fpt or ghec %}
|
||||
{% data reusables.user-settings.keeping_your_email_address_private %}{% endif %}
|
||||
|
||||
## Setting your commit email address in Git
|
||||
|
||||
You can use the `git config` command to change the email address you associate with your Git commits. The new email address you set will be visible in any future commits you push to {% data variables.location.product_location %} from the command line. Any commits you made prior to changing your commit email address are still associated with your previous email address.
|
||||
|
||||
### Setting your email address for every repository on your computer
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. {% data reusables.user-settings.set_your_email_address_in_git %}
|
||||
```shell
|
||||
$ git config --global user.email "YOUR_EMAIL"
|
||||
```
|
||||
3. {% data reusables.user-settings.confirm_git_email_address_correct %}
|
||||
```shell
|
||||
$ git config --global user.email
|
||||
<span class="output">email@example.com</span>
|
||||
```
|
||||
4. {% data reusables.user-settings.link_email_with_your_account %}
|
||||
|
||||
### Setting your email address for a single repository
|
||||
|
||||
{% data variables.product.product_name %} uses the email address set in your local Git configuration to associate commits pushed from the command line with your account on {% data variables.location.product_location %}.
|
||||
|
||||
You can change the email address associated with commits you make in a single repository. This will override your global Git configuration settings in this one repository, but will not affect any other repositories.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. Change the current working directory to the local repository where you want to configure the email address that you associate with your Git commits.
|
||||
3. {% data reusables.user-settings.set_your_email_address_in_git %}
|
||||
```shell
|
||||
$ git config user.email "YOUR_EMAIL"
|
||||
```
|
||||
4. {% data reusables.user-settings.confirm_git_email_address_correct %}
|
||||
```shell
|
||||
$ git config user.email
|
||||
<span class="output">email@example.com</span>
|
||||
```
|
||||
5. {% data reusables.user-settings.link_email_with_your_account %}
|
||||
@@ -0,0 +1,60 @@
|
||||
---
|
||||
title: Arten der von GitHub versendeten E-Mails
|
||||
intro: 'Du kannst von {% data variables.product.product_name %} verschiedene Arten von E-Mails erhalten, unter anderem Benachrichtigungen, Kontoinformationen, Einladungen zu Kundenforschungen und Marketingkommunikation.'
|
||||
redirect_from:
|
||||
- /articles/types-of-emails-github-sends
|
||||
- /github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
- Notifications
|
||||
shortTitle: Emails from GitHub
|
||||
ms.openlocfilehash: 0e03038c272f2815fd4427f73110641aa57b7028
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145164857'
|
||||
---
|
||||
## E-Mail-Benachrichtigungen
|
||||
|
||||
Du kannst festlegen, ob und welche Aktivitätsbenachrichtigungen du via E-Mail erhalten willst. Weitere Informationen findest du unter [Informationen zu Benachrichtigungen](/github/managing-subscriptions-and-notifications-on-github/about-notifications). Benachrichtigungs-E-Mails können folgendes beinhalten:
|
||||
|
||||
- Sicherheitsrelevante Aktivitäten an Repositorys, auf die du Administratorzugriff hast
|
||||
- Aktivitäten in von Dir beobachteten Repositorys
|
||||
- Unterhaltungen, an denen du teilnimmst
|
||||
- Unterhaltungen, in denen du @erwähnt (@mentioned) wurdest
|
||||
- Pushes an Pull Requests, an denen du mitwirkst
|
||||
- Einladungen zur Mitarbeit in einer Organisation oder an einem Repository
|
||||
- Deine eigenen Aktivitäten, beispielsweise das Öffnen, Kommentieren oder Schließen von Issues und Pull Requests
|
||||
|
||||
Auch kannst du die Art der E-Mail-Aktualisierungen festlegen, die du zu Unterhaltungen erhältst, die du beobachtest oder an denen du teilnimmst. Weitere Informationen findest du unter [Konfigurieren von Benachrichtigungen](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications).
|
||||
|
||||
## E-Mails der Organisation
|
||||
|
||||
Falls du ein Upgrade auf bezahlte Produkte oder Funktionen durchgeführt hast, erhältst du an die primäre E-Mail-Adresse deines Kontos Abrechnungsquittungen. Weitere Informationen findest du unter [Festlegen deiner Rechnungs-E-Mail-Adresse](/articles/setting-your-billing-email).
|
||||
|
||||
## E-Mails zur Kundenforschung
|
||||
|
||||
{% data variables.product.product_name %} sucht gelegentlich Kund*innen, die an Recherchesitzungen teilnehmen, um uns dabei zu helfen, GitHub noch besser zu machen. Diese werden remote durchgeführt, und Kund*innen aus der ganzen Welt können daran teilnehmen. Folgende Bereiche können enthalten sein:
|
||||
|
||||
- Feedbackumfragen
|
||||
- Forschungsinterviews
|
||||
- Tests zur Benutzerfreundlichkeit
|
||||
- Vorschau zu frühen Prototypen oder Konzepten
|
||||
|
||||
Diese E-Mails werden nicht oft verschickt, und du entscheidest, ob du teilnehmen möchtest. Wenn du an weiteren Möglichkeiten interessiert bist, an Recherchesitzungen teilzunehmen, kannst du dich beim GitHub Customer Research Panel anmelden. Weitere Informationen findest du unter [GitHub-Recherche zur Kundenfreundlichkeit](https://cxr.github.com).
|
||||
|
||||
## Marketing-E-Mails
|
||||
|
||||
{% data variables.product.product_name %} versendet gelegentlich auch E-Mails mit folgenden Arten von Marketingkommunikation:
|
||||
|
||||
- Tipps und Tricks für die ersten Schritte mit deinem Konto
|
||||
- Persönlich abgestimmte Informationen zu interessanten neuen Projekten oder Funktionen
|
||||
- Abonnierte Newsletter wie {% data variables.explore.explore_github %}
|
||||
|
||||
Weitere Informationen findest du unter [Verwalten von Marketing-E-Mails aus GitHub](/articles/managing-marketing-emails-from-github).
|
||||
@@ -0,0 +1,99 @@
|
||||
---
|
||||
title: Informationen zum persönlichen Dashboard
|
||||
redirect_from:
|
||||
- /hidden/about-improved-navigation-to-commonly-accessed-pages-on-github
|
||||
- /articles/opting-into-the-public-beta-for-a-new-dashboard
|
||||
- /articles/about-your-personal-dashboard
|
||||
- /github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard
|
||||
intro: 'Über dein persönliches Dashboard kannst du über Issues und Pull Requests, die du bearbeitest oder verfolgst, auf dem Laufenden bleiben .Du kannst zu deinen wichtigsten Repositorys und Teamseiten navigieren, dich über die neuesten Aktivitäten in Organisationen und Repositorys informieren, die du abonniert hast, und empfohlene Repositorys erkunden.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Your personal dashboard
|
||||
ms.openlocfilehash: ee22085e669eedec2e0a9f298cc4d5ad144316c6
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146179151'
|
||||
---
|
||||
## Auf dein persönliches Dashboard zugreifen
|
||||
|
||||
Dein persönliches Dashboard ist die erste Seite, die du siehst, wenn du dich bei {% data variables.product.product_name %} anmeldest.
|
||||
|
||||
Wenn du nach der Anmeldung auf dein persönliches Dashboard zugreifen möchtest, klicke auf das {% octicon "mark-github" aria-label="The github octocat logo" %}-Logo in der oberen linken Ecke einer beliebigen Seite auf {% data variables.product.product_name %}.
|
||||
|
||||
## Neueste Aktivitäten finden
|
||||
|
||||
Im Abschnitt „Recent activity“ (Neueste Aktivitäten) deines Newsfeed kannst du schnell die zuletzt aktualisierten Issues und Pull Requests, an denen du arbeitest, finden und weiterverfolgen. Im Abschnitt „Letzte Aktivität“ kannst du bis zu vier der letzten Aktualisierungen anzeigen, die in den vergangenen zwei Wochen erfolgt sind.
|
||||
|
||||
{% data reusables.dashboard.recent-activity-qualifying-events %}
|
||||
|
||||
## Deine wichtigsten Repositorys und Teams finden
|
||||
|
||||
Über die linke Seitenleiste deines Dashboards kannst du auf die wichtigsten Repositorys und Teams zugreifen, die du verwendest.
|
||||
|
||||
|
||||
|
||||
Die Liste der wichtigsten Repositorys wird automatisch generiert und kann jedes Repository enthalten, mit dem du interagiert hast, unabhängig davon, ob es sich direkt im Besitz deines Kontos befindet oder nicht. Zu diesen Interaktionen gehören das Durchführen von Commits oder das Erstellen oder Kommentieren von Issues und Pull Requests. Die Liste der wichtigsten Repositorys kann nicht bearbeitet werden. Die Repositorys werden vier Monate, nachdem du das letzte Mal mit ihnen interagiert hast, von der Liste genommen.
|
||||
|
||||
Wenn du oben auf einer beliebigen Seite auf {% data variables.product.product_name %} in die Suchleiste klickst, findest du außerdem eine Liste deiner zuletzt aufgerufenen Repositorys, Teams und Projektboards.
|
||||
|
||||
## Über Aktivitäten in der Community auf dem Laufenden bleiben
|
||||
|
||||
{% ifversion for-you-feed %} Im Hauptabschnitt deines Dashboards gibt es zwei Aktivitätsfeeds:
|
||||
|
||||
- Ich folge: Aktivitäten von Personen und Repositorys, denen du folgst
|
||||
- Für dich: Aktivitäten und Empfehlungen, die auf deinem {% data variables.product.product_name %}-Netzwerk basieren
|
||||
|
||||
### Der Feed „Ich folge“
|
||||
|
||||
In diesem Feed werden Aktivitäten von Repositorys und Benutzer*innen angezeigt, an denen du Interesse gezeigt hast, da du dem*der Benutzer*in oder einem Repository folgst. So werden beispielsweise Updates angezeigt, wenn Benutzer*innen, denen du folgst, Folgendes tun:
|
||||
|
||||
{% else %} Im Abschnitt „Alle Aktivitäten“ deines Newsfeeds kannst du Updates zu Repositorys und Benutzer*innen anzeigen, denen du folgst.
|
||||
|
||||
In deinem Newsfeed werden Updates angezeigt, wenn Benutzer*innen, denen du folgst, Folgendes tun: {% endif %}
|
||||
|
||||
|
||||
- Ein Repository mit einem Stern versieht.
|
||||
- Anderen Benutzer*innen folgen{% ifversion fpt or ghes or ghec %}
|
||||
- Ein öffentliches Repository erstellen{% endif %}
|
||||
- Einen Issue oder Pull Request mit der Kennzeichnung „help wanted“ oder „good first issue“ in einem von Dir beobachteten Repository öffnet.
|
||||
- Commits an ein Repository pushen, dem du folgst{% ifversion fpt or ghes or ghec %}
|
||||
- Ein öffentliches Repository forken{% endif %}
|
||||
- Ein neues Release veröffentlichen
|
||||
|
||||
Weitere Informationen zum Folgen von Personen und Repositorys findest du unter [Folgen von Personen](/get-started/exploring-projects-on-github/following-people) und [Zusammenarbeit](/get-started/quickstart/be-social).
|
||||
|
||||
{% ifversion for-you-feed %}
|
||||
### Der Feed „Für dich“
|
||||
|
||||
{% note %}
|
||||
|
||||
**Hinweis:** Diese neue Registerkarte befindet sich derzeit in der öffentlichen Betaversion und kann geändert werden.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
In diesem Feed werden Aktivitäten und Empfehlungen angezeigt, die auf deinem Netzwerk auf {% data variables.product.product_name %} basieren. Dieser dient dazu, interessante Updates anzuzeigen, dich auf dem neuesten Stand zu halten und dir zu helfen, neue Communitys zu finden, an denen du teilhaben möchtest. Dein Netzwerk umfasst:
|
||||
|
||||
- Repositorys, die du mit einem Stern markiert hast
|
||||
- Repositorys, zu denen du beigetragen hast
|
||||
- Benutzer*innen, denen du folgst oder die du finanziell unterstützt
|
||||
- Benutzer*innen, mit denen du zusammengearbeitet hast
|
||||
- Organisationen, denen du folgst
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Empfohlene Repositorys erkunden
|
||||
|
||||
Im Abschnitt "Explore repositories" (Repositories erkunden) auf der rechten Seite deines Dashboards kannst du empfohlene Repositorys in deinen Communities erkunden. Die Empfehlungen basieren darauf, welche Repositorys du mit einem Stern markiert oder besucht hast, welchen Personen du folgst und auf welche Repositorys du Zugriff hast.{% ifversion fpt or ghec %} Weitere Informationen findest du unter [Beitragen zu Open-Source-Projekten auf {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github).{% endif %}
|
||||
|
||||
## Weiterführende Themen
|
||||
|
||||
- [Informationen zum Dashboard deiner Organisation](/articles/about-your-organization-dashboard)
|
||||
@@ -0,0 +1,97 @@
|
||||
---
|
||||
title: Changing your GitHub username
|
||||
intro: 'You can change the username for your account on {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.location.product_location %} if your instance uses built-in authentication{% endif %}.'
|
||||
redirect_from:
|
||||
- /articles/how-to-change-your-username
|
||||
- /articles/changing-your-github-user-name
|
||||
- /articles/renaming-a-user
|
||||
- /articles/what-happens-when-i-change-my-username
|
||||
- /articles/changing-your-github-username
|
||||
- /github/setting-up-and-managing-your-github-user-account/changing-your-github-username
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Change your username
|
||||
---
|
||||
|
||||
{% ifversion ghec or ghes %}
|
||||
|
||||
{% note %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
**Note**: Members of an {% data variables.enterprise.prodname_emu_enterprise %} cannot change usernames. Your enterprise's IdP administrator controls your username for {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
**Note**: If you sign into {% data variables.location.product_location %} with LDAP credentials or single sign-on (SSO), only your local administrator can change your username. For more information about authentication methods for {% data variables.product.product_name %}, see "[Authenticating users for {% data variables.location.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## About username changes
|
||||
|
||||
You can change your username to another username that is not currently in use.{% ifversion fpt or ghec %} If the username you want is not available, consider other names or unique variations. Using a number, hyphen, or an alternative spelling might help you find a similar username that's still available.
|
||||
|
||||
If you hold a trademark for the username, you can find more information about making a trademark complaint on our [Trademark Policy](/free-pro-team@latest/github/site-policy/github-trademark-policy) page.
|
||||
|
||||
If you do not hold a trademark for the name, you can choose another username or keep your current username. {% data variables.contact.github_support %} cannot release the unavailable username for you. For more information, see "[Changing your username](#changing-your-username)."{% endif %}
|
||||
|
||||
After changing your username, your old username becomes available for anyone else to claim. Most references to your repositories under the old username automatically change to the new username. However, some links to your profile won't automatically redirect.
|
||||
|
||||
{% data variables.product.product_name %} cannot set up redirects for:
|
||||
- [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) using your old username
|
||||
- Links to [gists](/articles/creating-gists) that include your old username
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you cannot make changes to your username. {% data reusables.enterprise-accounts.emu-more-info-account %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Repository references
|
||||
|
||||
After you change your username, {% data variables.product.product_name %} will automatically redirect references to your repositories.
|
||||
- Web links to your existing repositories will continue to work. This can take a few minutes to complete after you make the change.
|
||||
- Command line pushes from your local repository clones to the old remote tracking URLs will continue to work.
|
||||
|
||||
If the new owner of your old username creates a repository with the same name as your repository, that will override the redirect entry and your redirect will stop working. Because of this possibility, we recommend you update all existing remote repository URLs after changing your username. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
|
||||
|
||||
## Links to your previous profile page
|
||||
|
||||
After changing your username, links to your previous profile page, such as `https://{% data variables.command_line.backticks %}/previoususername`, will return a 404 error. We recommend updating any links to your account on {% data variables.location.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}.
|
||||
|
||||
## Your Git commits
|
||||
|
||||
{% ifversion fpt or ghec %}Git commits that were associated with your {% data variables.product.product_name %}-provided `noreply` email address won't be attributed to your new username and won't appear in your contributions graph.{% endif %} If your Git commits are associated with another email address you've [added to your GitHub account](/articles/adding-an-email-address-to-your-github-account), {% ifversion fpt or ghec %}including the ID-based {% data variables.product.product_name %}-provided `noreply` email address, {% endif %}they'll continue to be attributed to you and appear in your contributions graph after you've changed your username. For more information on setting your email address, see "[Setting your commit email address](/articles/setting-your-commit-email-address)."
|
||||
|
||||
## Your gists
|
||||
|
||||
After changing your username, the URLs to any public or secret gists will also change and previous links to these will return a 404 error. We recommend updating the links to these gists anywhere you may have shared them.
|
||||
|
||||
## Changing your username
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.account_settings %}
|
||||
3. In the "Change username" section, click **Change username**.
|
||||
{% ifversion fpt or ghec %}
|
||||
4. Read the warnings about changing your username. If you still want to change your username, click **I understand, let's change my username**.
|
||||
|
||||
5. Type a new username.
|
||||
|
||||
6. If the username you've chosen is available, click **Change my username**. If the username you've chosen is unavailable, you can try a different username or one of the suggestions you see.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Why are my commits linked to the wrong user?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)"{% ifversion fpt or ghec %}
|
||||
- "[{% data variables.product.prodname_dotcom %} Username Policy](/free-pro-team@latest/github/site-policy/github-username-policy)"{% endif %}
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: Benutzerkontoeinstellungen verwalten
|
||||
intro: 'Du kannst die Einstellungen für dein persönliches Konto verwalten, einschließlich Thema, Benutzername, Standardbranche, Barrierefreiheit und Sicherheitseinstellungen.'
|
||||
redirect_from:
|
||||
- /categories/29/articles
|
||||
- /categories/user-accounts
|
||||
- /articles/managing-user-account-settings
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
children:
|
||||
- /about-your-personal-dashboard
|
||||
- /managing-your-theme-settings
|
||||
- /managing-your-tab-size-rendering-preference
|
||||
- /changing-your-github-username
|
||||
- /permission-levels-for-a-personal-account-repository
|
||||
- /permission-levels-for-a-project-board-owned-by-a-personal-account
|
||||
- /managing-accessibility-settings
|
||||
- /managing-the-default-branch-name-for-your-repositories
|
||||
- /managing-security-and-analysis-settings-for-your-personal-account
|
||||
- /managing-access-to-your-personal-accounts-project-boards
|
||||
- /managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages
|
||||
- /integrating-jira-with-your-personal-projects
|
||||
- /what-does-the-available-for-hire-checkbox-do
|
||||
shortTitle: Personal account settings
|
||||
ms.openlocfilehash: fcb653fa2fd40c206deefdaf967bae6104393537
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147760863'
|
||||
---
|
||||
|
||||
@@ -0,0 +1,30 @@
|
||||
---
|
||||
title: Integrating Jira with your personal projects
|
||||
intro: 'You can integrate Jira Cloud with your personal account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues.'
|
||||
redirect_from:
|
||||
- /articles/integrating-jira-with-your-personal-projects
|
||||
- /github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
shortTitle: Integrate Jira with projects
|
||||
---
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.developer_settings %}
|
||||
{% data reusables.user-settings.oauth_apps %}
|
||||
1. Click **Register a new application**.
|
||||
2. Under **Application name**, type "Jira".
|
||||
3. Under **Homepage URL**, type the full URL to your Jira instance.
|
||||
4. Under **Authorization callback URL**, type the full URL to your Jira instance.
|
||||
5. Click **Register application**.
|
||||
|
||||
8. Under **Developer applications**, note the "Client ID" and "Client Secret" values.
|
||||
|
||||
{% data reusables.user-settings.jira_help_docs %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- ["Integrating Jira with your organization project board"](/articles/integrating-jira-with-your-organization-project-board)
|
||||
- <a href="https://confluence.atlassian.com/adminjiracloud/connect-jira-cloud-to-github-814188429.html" data-proofer-ignore>Connect Jira Cloud to GitHub</a> (Atlassian documentation)
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: Verwalten des Zugriffs auf die Projektboards deines persönlichen Kontos
|
||||
intro: Als Projektboard-Inhaber kannst du einen Mitarbeiter hinzufügen oder entfernen und seine Berechtigungen für das Projektboard anpassen.
|
||||
redirect_from:
|
||||
- /articles/managing-project-boards-in-your-repository-or-organization
|
||||
- /articles/managing-access-to-your-user-account-s-project-boards
|
||||
- /articles/managing-access-to-your-user-accounts-project-boards
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Manage access project boards
|
||||
ms.openlocfilehash: 4cbf968cee79ac8e4aafbc5eea8220949cf80a30
|
||||
ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/12/2022
|
||||
ms.locfileid: '145164938'
|
||||
---
|
||||
Ein Mitarbeiter ist eine Person, die Berechtigungen für eines Deiner Projektboards besitzt. Die Berechtigung eines Mitarbeiters ist standardmäßig der Lesezugriff. Weitere Informationen findest du unter [Berechtigungsstufen für benutzereigene Projektboards](/articles/permission-levels-for-user-owned-project-boards).
|
||||
|
||||
## Mitarbeiter in ein Benutzer-Projektboard einladen
|
||||
|
||||
1. Navigiere zu dem Projektboard, zu dem Du einen Mitarbeiter hinzufügen möchtest.
|
||||
{% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %}
|
||||
5. Gib unter „Search by username, full name or email address“ (Nach Benutzernamen, vollständigem Namen oder E-Mail-Adresse suchen) den Namen, den Benutzernamen oder die {% data variables.product.prodname_dotcom %}-E-Mail-Adresse des Mitarbeiters ein.
|
||||
 {% data reusables.project-management.add-collaborator %}
|
||||
7. Der neue Mitarbeiter besitzt standardmäßig Leseberechtigung. Wähle optional im Dropdownmenü neben dem Namen des neuen Mitarbeiters eine andere Berechtigungsebene aus.
|
||||
|
||||
|
||||
## Mitarbeiter aus einem Benutzer-Projektboard entfernen
|
||||
|
||||
{% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.remove-collaborator %}
|
||||
@@ -0,0 +1,54 @@
|
||||
---
|
||||
title: Verwalten von Barrierefreiheitseinstellungen
|
||||
shortTitle: Manage accessibility settings
|
||||
intro: 'Die Benutzeroberfläche von {% data variables.product.product_name %} kann an deine visuellen, auditiven, motorischen, kognitiven oder lernspezifischen Bedürfnisse angepasst werden.'
|
||||
versions:
|
||||
feature: keyboard-shortcut-accessibility-setting
|
||||
redirect_from:
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings
|
||||
type: how_to
|
||||
miniTocMaxHeadingLevel: 3
|
||||
ms.openlocfilehash: 088bb097004f6c3b13412ec9716665b1f02edca5
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107213'
|
||||
---
|
||||
## Informationen zu Barrierefreiheitseinstellungen
|
||||
|
||||
Um eine Benutzeroberfläche auf {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} zu erstellen, die deinen Anforderungen entspricht, kannst du die Benutzeroberfläche anpassen. Barrierefreiheitseinstellungen können für Personen mit Behinderungen unerlässlich, aber für jeden nützlich sein. Die Anpassung von Tastenkombinationen ist beispielsweise für Personen wichtig, die mit der Sprachsteuerung navigieren, kann aber für jeden nützlich sein, wenn eine Tastenkombination für {% data variables.product.product_name %} mit einer Tastenkombination einer anderen Anwendung im Konflikt steht.
|
||||
|
||||
## Verwalten von Barrierefreiheitseinstellungen
|
||||
|
||||
Du kannst entscheiden, ob du einige oder alle Tastenkombinationen auf {% ifversion fpt or ghec %}{% data variables.location.product_location %}{% elsif ghes or ghae %}der Website für {% data variables.location.product_location %}{% endif %} verwenden möchtest, und du kannst die Anzeige animierter Bilder steuern.
|
||||
|
||||
### Verwalten von Tastenkombinationen
|
||||
|
||||
Du kannst Aktionen auf der {% data variables.product.product_name %}-Website ausschließlich mit der Tastatur ausführen. Tastenkombinationen können nützlich sein, um Zeit zu sparen, doch sie können versehentlich aktiviert werden oder Hilfstechnologie beeinträchtigen.
|
||||
|
||||
Standardmäßig sind alle Tastenkombinationen für {% data variables.product.product_name %} aktiviert. Weitere Informationen findest du unter [Tastenkombinationen](/get-started/using-github/keyboard-shortcuts).
|
||||
|
||||
{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.accessibility_settings %}
|
||||
1. Verwalte unter „Tastenkombinationen“ die Einstellungen für deine Tastenkombinationen.
|
||||
|
||||
- Um Tastenkombinationen zu deaktivieren, die keine Zusatztasten wie <kbd>Steuerelement</kbd> oder <kbd>Befehl</kbd> verwenden, deaktiviere unter „Allgemein“ die Option **Zeichentasten**.
|
||||
- Wenn du Zeichentasten deaktivierst, kannst du möglicherweise dennoch Tastenkombinationen für deinen Webbrowser auslösen, und du kannst weiterhin Tastenkombinationen für {% data variables.product.product_name %} auslösen, die eine Zusatztaste verwenden.
|
||||
{%- ifversion command-palette %}
|
||||
- Um die Tastenkombinationen zum Auslösen der Befehlspalette anzupassen, kannst du in den Dropdownmenüs unter „Befehlspalette“ eine Tastenkombination wählen. Weitere Informationen findest du unter [{% data variables.product.company_short %}-Befehlspalette](/get-started/using-github/github-command-palette).
|
||||
{%- endif %}
|
||||
|
||||
{% ifversion motion-management %}
|
||||
|
||||
### Verwalten von Bewegung
|
||||
|
||||
Du kannst steuern, wie {% data variables.product.product_name %} animierte _GIF_-Bilder anzeigt.
|
||||
|
||||
Standardmäßig ist {% data variables.product.product_name %} mit deiner Einstellung auf Systemebene für reduzierte Bewegung synchronisiert. Weitere Informationen findest du in der Dokumentation oder in den Einstellungen deines Betriebssystems.
|
||||
|
||||
{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.accessibility_settings %}
|
||||
1. Verwalte unter „Bewegung“ Einstellungen für Bewegung.
|
||||
|
||||
- Unter „Animierte Bilder automatisch wiedergeben“ kannst du steuern, wie in {% data variables.product.product_name %} animierte Bilder angezeigt werden sollen: **Synchron mit System**, **Aktiviert** oder **Deaktiviert**.
|
||||
|
||||
{% endif %}
|
||||
@@ -0,0 +1,54 @@
|
||||
---
|
||||
title: Managing security and analysis settings for your personal account
|
||||
intro: 'You can control features that secure and analyze the code in your projects on {% data variables.product.prodname_dotcom %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account
|
||||
shortTitle: Manage security & analysis
|
||||
---
|
||||
## About management of security and analysis settings
|
||||
|
||||
{% data variables.product.prodname_dotcom %} can help secure your repositories. This topic tells you how you can manage the security and analysis features for all your existing or new repositories.
|
||||
|
||||
You can still manage the security and analysis features for individual repositories. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
|
||||
|
||||
You can also review the security log for all activity on your personal account. For more information, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)."
|
||||
|
||||
{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
|
||||
|
||||
{% data reusables.security.security-and-analysis-features-enable-read-only %}
|
||||
|
||||
For an overview of repository-level security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."
|
||||
|
||||
## Enabling or disabling features for existing repositories
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.security-analysis %}
|
||||
3. Under "Code security and analysis", to the right of the feature, click **Disable all** or **Enable all**.
|
||||
{% ifversion ghes %}{% else %}{% endif %}
|
||||
6. Optionally, enable the feature by default for new repositories that you own.
|
||||
{% ifversion ghes %}{% else %}{% endif %}
|
||||
7. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories you own.
|
||||
{% ifversion ghes %}{% else %}{% endif %}
|
||||
|
||||
{% data reusables.security.displayed-information %}
|
||||
|
||||
## Enabling or disabling features for new repositories
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.security-analysis %}
|
||||
3. Under "Code security and analysis", to the right of the feature, enable or disable the feature by default for new repositories that you own.
|
||||
{% ifversion ghes %}{% else %}{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
|
||||
- "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
|
||||
- "[Keeping your dependencies updated automatically](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically)"
|
||||
@@ -0,0 +1,36 @@
|
||||
---
|
||||
title: Managing the default branch name for your repositories
|
||||
intro: 'You can set the default branch name for new repositories that you create on {% data variables.location.product_location %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories
|
||||
shortTitle: Manage default branch name
|
||||
---
|
||||
## About management of the default branch name
|
||||
|
||||
When you create a new repository on {% data variables.location.product_location %}, the repository contains one branch, which is the default branch. You can change the name that {% data variables.product.product_name %} uses for the default branch in new repositories you create. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)."
|
||||
|
||||
{% data reusables.branches.change-default-branch %}
|
||||
|
||||
## Setting the default branch name
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.repo-tab %}
|
||||
3. Under "Repository default branch", click **Change default branch name now**.
|
||||
|
||||
4. Type the default name that you would like to use for new branches.
|
||||
|
||||
5. Click **Update**.
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)"
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
title: Verwalten deiner Cookieeinstellungen für die Unternehmensmarketingseiten von GitHub
|
||||
intro: 'Du kannst steuern, wie {% data variables.product.company_short %} Informationen aus nicht essenziellen Nachverfolgungscookies für Unternehmensmarketingseiten verwendet.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Manage cookie preferences
|
||||
ms.openlocfilehash: 44f0324a91f8447a10947d5f5c7be111241ad091
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148108290'
|
||||
---
|
||||
## Informationen zu Cookieeinstellungen auf Unternehmensmarketingseiten
|
||||
|
||||
{% data variables.product.company_short %} kann auf einigen Unternehmensmarketingseiten nicht essenzielle Cookies verwenden. Du kannst anpassen, wie sich diese Cookies verhalten. Weitere Informationen dazu, wie {% data variables.product.company_short %} Cookies verwendet, findest du in den [{% data variables.product.company_short %}-Datenschutzbestimmungen](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement).
|
||||
|
||||
## Ändern deiner Cookieeinstellungen
|
||||
|
||||
Du kannst anpassen, wie sich nicht essenzielle Cookies auf einer {% data variables.product.company_short %}-Unternehmensmarketingseite verhalten.
|
||||
|
||||
1. Navigiere zu der {% data variables.product.company_short %}-Unternehmensmarketingseite, auf der du deine Cookieeinstellungen ändern möchtest. Navigiere beispielsweise zu [{% data variables.product.company_short %}-Ressourcen](https://resources.github.com/).
|
||||
1. Scrolle zum unteren Ende der Seite, und klicke dann auf **Cookies verwalten**.
|
||||
|
||||
|
||||
|
||||
1. Klicke unter „Cookieeinstellungen verwalten“ auf **Annehmen** oder **Ablehnen**, um jedes nicht essenzielle Cookie anzunehmen oder abzulehnen.
|
||||
|
||||
|
||||
|
||||
1. Klicke auf **Änderungen speichern**.
|
||||
|
||||
|
||||
@@ -0,0 +1,26 @@
|
||||
---
|
||||
title: Verwalten der Renderingeinstellungen für die Tabulatorgröße
|
||||
intro: 'Du kannst die Anzahl von Leerzeichen verwalten, die einer Registerkarte für dein persönliches Konto entspricht.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghae: '>= 3.4'
|
||||
ghes: '>=3.4'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Managing your tab size
|
||||
redirect_from:
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference
|
||||
ms.openlocfilehash: e3188b508e5ffb84266bc4b7689a5cbc16aa07de
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145165005'
|
||||
---
|
||||
Wenn du der Meinung bist, dass der Tabulatoreinzug in Code, der in {% data variables.product.product_name %} gerendert wird, zu groß oder zu klein ist, kannst du dies in den Einstellungen ändern.
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
1. Klicke in der linken Seitenleiste auf **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Darstellung**.
|
||||
2. Klicke unter „Einstellung der Tabulatorgröße“ auf das Dropdownmenü, und wähle die gewünschte Einstellung aus.
|
||||
|
||||
@@ -0,0 +1,63 @@
|
||||
---
|
||||
title: Managing your theme settings
|
||||
intro: 'You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses a light or dark mode.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghae: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings
|
||||
shortTitle: Manage theme settings
|
||||
---
|
||||
|
||||
For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from themes that are light or dark, or you can configure {% data variables.product.product_name %} to follow your system settings.
|
||||
|
||||
You may want to use a dark theme to reduce power consumption on certain devices, to reduce eye strain in low-light conditions, or because you prefer how the theme looks.
|
||||
|
||||
If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% ifversion fpt or ghae or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.appearance-settings %}
|
||||
|
||||
1. Under "Theme mode", select the drop-down menu, then click a theme preference.
|
||||
|
||||
|
||||
1. Click the theme you'd like to use.
|
||||
- If you chose a single theme, click a theme.
|
||||
|
||||
{%- ifversion ghes = 3.5 %}
|
||||
{% note %}
|
||||
|
||||
**Note**: The light high contrast theme was unavailable in {% data variables.product.product_name %} 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The theme is available in 3.5.4 and later. For more information about upgrades, contact your site administrator.
|
||||
|
||||
For more information about determining the version of {% data variables.product.product_name %} you're using, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
|
||||
{% endnote %}
|
||||
{%- endif %}
|
||||
|
||||
|
||||
- If you chose to follow your system settings, click a day theme and a night theme.
|
||||
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
- If you would like to choose a theme which is currently in public beta, you will first need to enable it with feature preview. For more information, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."{% endif %}
|
||||
|
||||
{% ifversion command-palette %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You can also change your theme settings with the command palette. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)".
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Setting a theme for {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)"
|
||||
@@ -0,0 +1,98 @@
|
||||
---
|
||||
title: Berechtigungsebenen für ein Repository in einem persönlichen Konto
|
||||
intro: Ein Repository im Besitz eines persönlichen Kontos verfügt über die beiden Berechtigungsstufen Repositorybesitzer und Mitarbeiter.
|
||||
redirect_from:
|
||||
- /articles/permission-levels-for-a-user-account-repository
|
||||
- /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Repository permissions
|
||||
ms.openlocfilehash: dd2124c23054fa7bd44bb6501dae4363e59bab75
|
||||
ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 10/27/2022
|
||||
ms.locfileid: '148113873'
|
||||
---
|
||||
## Informationen zu Berechtigungsebenen für ein Repository eines persönlichen Kontos
|
||||
|
||||
Repositorys im Besitz persönlicher Konten haben jeweils nur einen Besitzer. Besitzberechtigungen können nicht mit einem anderen persönlichen Konto geteilt werden.
|
||||
|
||||
Du kannst deinem Repository auch Benutzer*innen auf {% data variables.product.product_name %} als Projektmitarbeiter*innen {% ifversion fpt or ghec %}invite{% else %}hinzufügen{% endif %}. Weitere Informationen findest du unter [Einladen von Projektmitarbeiter*innen zu einem persönlichen Repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository).
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tipp:** Wenn du einen detaillierteren Zugriff auf ein Repository benötigst, das zu deinem persönlichen Konto gehört, kannst du das Repository an eine Organisation übertragen. Weitere Informationen findest du unter [Übertragen eines Repositorys](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account).
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## Besitzerzugriff auf ein Repository im Besitz eines persönlichen Kontos
|
||||
|
||||
Der Repository-Inhaber besitzt die vollständige Kontrolle über das Repository. Zusätzlich zu den Aktionen, die jede*r Projektmitarbeiter*in ausführen kann, kann der oder die Repositorybesitzer*in die folgenden Aktionen ausführen.
|
||||
|
||||
| Aktion | Weitere Informationen |
|
||||
| :- | :- |
|
||||
| {% ifversion fpt or ghec %}Einladen von Projektmitarbeiter*innen{% else %}Hinzufügen von Projektmitarbeiter*innen{% endif %} | [Einladen von Projektmitarbeiter*innen in ein persönliches Repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository) |
|
||||
| Ändern der Sichtbarkeit des Repositorys | [Festlegen der Sichtbarkeit eines Repository](/github/administering-a-repository/setting-repository-visibility) |{% ifversion fpt or ghec %}
|
||||
| Einschränken von Interaktionen mit dem Repository | [Einschränken von Interaktionen mit dem Repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) |{% endif %}
|
||||
| Umbenennen eines Branchs, einschließlich des Standardbranchs | [Umbenennen eines Branchs](/github/administering-a-repository/renaming-a-branch) |
|
||||
| Einen Pull Request auf einem geschützten Branch zusammenführen, selbst ohne genehmigende Reviews | [Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches) |
|
||||
| Das Repository löschen | [Löschen eines Repositorys](/repositories/creating-and-managing-repositories/deleting-a-repository) |
|
||||
| Verwalten der Themen des Repositorys | [Klassifizieren deines Repositorys mit Themen](/github/administering-a-repository/classifying-your-repository-with-topics) |{% ifversion fpt or ghec %}
|
||||
| Verwalten von Sicherheits- und Analyseeinstellungen für das Repository | [Verwalten von Sicherheits- und Analyseeinstellungen für das Repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) |{% endif %}{% ifversion fpt or ghec %}
|
||||
| Aktivieren des Abhängigkeitsdiagramms für ein privates Repository | [Untersuchen der Abhängigkeiten eines Repositorys](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository) |{% endif %}
|
||||
| Löschen und Wiederherstellen von Paketen | [Löschen und Wiederherstellen eines Pakets](/packages/learn-github-packages/deleting-and-restoring-a-package) |
|
||||
| Anpassen der Social-Media-Vorschau des Repositorys | [Anpassen der Social-Media-Vorschau des Repositorys](/github/administering-a-repository/customizing-your-repositorys-social-media-preview) |
|
||||
| Erstellen einer Vorlage aus dem Repository | [Erstellen einer Repository-Vorlage](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository) |
|
||||
| Steuern des Zugriffs auf {% data variables.product.prodname_dependabot_alerts %}| [Verwalten von Sicherheits- und Analyseeinstellungen für dein Repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) |{% ifversion fpt or ghec %}
|
||||
| Verwerfen von {% data variables.product.prodname_dependabot_alerts %} im Repository | [Anzeigen und Aktualisieren von {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts) |
|
||||
| Verwalten der Datenverwendung für ein privates Repository | [Verwalten von Datenverwendungseinstellungen für dein privates Repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)|{% endif %}
|
||||
| Codeinhaber für das Repository definieren | [Informationen zu Codeinhabern](/github/creating-cloning-and-archiving-repositories/about-code-owners) |
|
||||
| Archiv des Repositorys | [Archivierung von Repositorys](/repositories/archiving-a-github-repository/archiving-repositories) |{% ifversion fpt or ghec %}
|
||||
| Erstellen von Sicherheitsempfehlungen | [Informationen zu Sicherheitsempfehlungen für Repositorys](/github/managing-security-vulnerabilities/about-github-security-advisories) |
|
||||
| Anzeigen einer Sponsorschaltfläche | [Anzeigen einer Sponsorschaltfläche in deinem Repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository) |{% endif %}
|
||||
| Zulassen oder Deaktivieren der automatischen Zusammenführung für Pull Requests | [Verwalten der automatischen Zusammenführung für Pull Requests in deinem Repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) |
|
||||
| Verwalten von Webhooks und Bereitstellen von Schlüsseln | [Verwalten von Bereitstellungsschlüsseln](/developers/overview/managing-deploy-keys#deploy-keys) |
|
||||
|
||||
## Projektmitarbeiterzugriff auf ein Repository im Besitz eines persönlichen Kontos
|
||||
|
||||
Projektmitarbeiter*innen in einem persönlichen Repository können den Inhalt des Repositorys pullen (lesen) und Änderungen an das Repository pushen (schreiben).
|
||||
|
||||
{% note %}
|
||||
|
||||
**Hinweis:** In einem privaten Repository können Repositorybesitzer*innen Projektmitarbeiter*innen ausschließlich Schreibzugriff gewähren. Projektmitarbeiter können keinen schreibgeschützten Zugriff auf Repositorys haben, die zu einem persönlichen Konto gehören.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Projektmitarbeiter*innen können auch folgende Aktionen durchführen.
|
||||
|
||||
| Aktion | Weitere Informationen |
|
||||
| :- | :- |
|
||||
| Forken des Repositorys | [Informationen zu Forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) |
|
||||
| Umbenennen eines anderen Branchs als der Standardbranch | [Umbenennen eines Branchs](/github/administering-a-repository/renaming-a-branch) |
|
||||
| Erstellen, Bearbeiten und Löschen von Kommentaren zu Commits, Pull Requests und Problemen im Repository | <ul><li>[Informationen zu Issues](/github/managing-your-work-on-github/about-issues)</li><li>[Kommentieren eines Pull Requests](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)</li><li>[Verwalten störender Kommentare](/communities/moderating-comments-and-conversations/managing-disruptive-comments)</li></ul> |
|
||||
| Erstellen, Zuweisen, Schließen und erneutes Öffnen von Issues im Repository | [Verwalten der Arbeit mit Issues](/github/managing-your-work-on-github/managing-your-work-with-issues) |
|
||||
| Verwalten von Bezeichnungen für Issues und Pull Requests im Repository | [Kennzeichnen von Issues und Pull Requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests) |
|
||||
| Verwalten von Meilensteinen für Issues und Pull Requests im Repository | [Erstellen und Bearbeiten von Meilensteinen für Issues und Pull Requests](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests) |
|
||||
| Markieren eines Issues oder Pull Requests im Repository als Duplikat | [Informationen zu Duplikaten von Issues und Pull Requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests) |
|
||||
| Erstellen, Zusammenführen und Schließen von Pull Requests im Repository | [Vorschlagen von Änderungen an deiner Arbeit mit Pull Requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests) |
|
||||
| Aktivieren und Deaktivieren der automatischen Zusammenführung für einen Pull Request | [Automatisches Zusammenführen eines Pull Requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)
|
||||
| Anwenden von vorgeschlagenen Änderungen an Pull Requests im Repository |[Aufnehmen von Feedback in deinem Pull Request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) |
|
||||
| Erstellen eines Pull Requests von einem Fork des Repositorys | [Erstellen eines Pull Requests vom einem Fork des Repositorys](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork) |
|
||||
| Übermitteln einer Überprüfung eines Pull Requests, der die Zusammenführungsfähigkeit des Pull Requests beeinflusst | [Überprüfen vorgeschlagener Änderungen in einem Pull Request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request) |
|
||||
| Erstellen und Bearbeiten eines Wikis für das Repository | [Informationen zu Wikis](/communities/documenting-your-project-with-wikis/about-wikis) |
|
||||
| Erstellen und Bearbeiten von Releases für das Repository | [Verwalten von Releases in einem Repository](/github/administering-a-repository/managing-releases-in-a-repository) |
|
||||
| Handeln als Codebesitzer*in für das Repository | [Informationen zu Codeinhabern](/articles/about-code-owners) |{% ifversion fpt or ghae or ghec %}
|
||||
| Veröffentlichen, Anzeigen oder Installieren von Paketen | [Veröffentlichen und Verwalten von Paketen](/github/managing-packages-with-github-packages/publishing-and-managing-packages) |{% endif %}
|
||||
| Sich selbst als Mitarbeiter aus dem Repository entfernen | [Sich selbst aus dem Repository eines Projektmitarbeiters entfernen](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository) |
|
||||
|
||||
## Weitere Informationsquellen
|
||||
|
||||
- [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)
|
||||
@@ -0,0 +1,70 @@
|
||||
---
|
||||
title: Berechtigungsstufen für ein Projektboard im Besitz eines persönlichen Kontos
|
||||
intro: 'Ein Projektboard im Besitz eines persönlichen Kontos verfügt über zwei Berechtigungsebenen: den Projektboardbesitzer und die Mitarbeiter*innen.'
|
||||
redirect_from:
|
||||
- /articles/permission-levels-for-user-owned-project-boards
|
||||
- /github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Project board permissions
|
||||
ms.openlocfilehash: 353b9ac497abc7110437aafdf691ca48a3ff6cec
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145165004'
|
||||
---
|
||||
## Zuweisen von Benutzerrollen und Berechtigungen
|
||||
|
||||
Es gibt nur einen Besitzer eines benutzereigenen Projektboards. Diese Berechtigung kann nicht mit einem anderen persönlichen Konto geteilt werden. Neben dem Inhaber können auch andere Personen an Projektboards mitarbeiten.
|
||||
|
||||
Für Projektboard-Mitarbeiter gibt es drei Berechtigungsstufen:
|
||||
|
||||
{% data reusables.project-management.project-board-permissions %}
|
||||
|
||||
## Inhaber- und Administratorberechtigungen für ein Benutzer-Projektboard
|
||||
|
||||
Der Projektboard-Inhaber und die Mitarbeiter mit Administratorzugriff besitzen die vollständige Kontrolle über das Projektboard. Neben den Berechtigungen, die auch Projektboard-Mitarbeitern erteilt werden, stehen einem Projektboard-Inhaber und Mitarbeitern mit Administratorzugriff zusätzlich folgende Möglichkeiten zur Verfügung:
|
||||
|
||||
- [Verwalten, Anzeigen und Hinzufügen von Mitarbeitern](/articles/managing-access-to-your-user-account-s-project-boards)
|
||||
- [Konfigurieren eines Projektboards als {% ifversion ghae %}intern{% else %}öffentlich{% endif %} oder privat](/articles/changing-project-board-visibility)
|
||||
- [Löschen eines Projektboards](/articles/deleting-a-project-board/)
|
||||
- [Schließen eines Projektboards](/articles/closing-a-project-board/)
|
||||
- [Erneutes Öffnen eines geschlossenen Projektboards](/articles/reopening-a-closed-project-board)
|
||||
|
||||
## Lese- und Schreibberechtigungen für ein Benutzer-Projektboard
|
||||
|
||||
Mitarbeiter mit Lesezugriff auf ein Benutzer-Projektboard können Folgendes tun:
|
||||
|
||||
- Ein Projektboard anzeigen
|
||||
- Ein Projektboard kopieren
|
||||
- Tickets auf einem Projektboard filtern
|
||||
|
||||
Mitarbeiter mit Schreibzugriff auf ein Benutzer-Projektboard können Folgendes tun:
|
||||
|
||||
- Ein Projektboard anzeigen
|
||||
- Ein Projektboard kopieren
|
||||
- Tickets auf einem Projektboard filtern
|
||||
- Ein Projektboard bearbeiten
|
||||
- Ein Repository mit einem Projektboard verknüpfen
|
||||
- Automatisierung für Projektboards konfigurieren
|
||||
- Ein Projektboard kopieren
|
||||
- Issues und Pull Requests zu einem Projektboard hinzufügen
|
||||
- Hinweise zu einem Projektboard hinzufügen
|
||||
- Fortschritt in deinem Projektboard verfolgen
|
||||
- Tickets auf einem Projektboard archivieren
|
||||
|
||||
## Sichtbarkeit des Projektboards
|
||||
|
||||
Du kannst die Sichtbarkeit des Projektboards von privat in {% ifversion ghae %}intern{% else %}öffentlich{% endif %} und wieder zurück ändern. Standardmäßig sind Benutzer-Projektboards privat. Weitere Informationen findest du unter [Ändern der Sichtbarkeit von Projektboards](/articles/changing-project-board-visibility).
|
||||
|
||||
## Weiterführende Themen
|
||||
|
||||
- [Verwalten des Zugriffs auf die Projektboards deines persönlichen Kontos](/articles/managing-access-to-your-user-account-s-project-boards)
|
||||
@@ -0,0 +1,34 @@
|
||||
---
|
||||
title: Funktionsweise des Kontrollkästchens „Available for hire“ (Zum Einstellen verfügbar)
|
||||
intro: 'Aktiviere das Kontrollkästchen **Auf Stellensuche**, um GitHub Jobs-Beiträge auf GitHub anzuzeigen.'
|
||||
redirect_from:
|
||||
- /articles/what-does-the-available-for-hire-checkbox-do
|
||||
- /github/setting-up-and-managing-your-github-user-account/what-does-the-available-for-hire-checkbox-do
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Available for hire checkbox
|
||||
ms.openlocfilehash: 1f7f188ae86093478385f7f569ec37c3479a7661
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145164952'
|
||||
---
|
||||
{% warning %}
|
||||
|
||||
Hinweis zur Veraltung: GitHub Jobs ist jetzt veraltet. Das letzte Datum zum Posten einer Stelle war der 19. Mai 2021. Die Website von GitHub Jobs wurde am 19. August 2021 vollständig abgeschaltet und weist nun eine Weiterleitung zum [GitHub-Blogbeitrag](https://github.blog/changelog/2021-04-19-deprecation-notice-github-jobs-site/) auf, in dem du weitere Informationen über die nun vollständige Abschaltung von GitHub Jobs findest.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
Das [GitHub Jobs](https://jobs.github.com/)-Board ist eine großartige Möglichkeit, eine Stelle in der IT-Branche zu finden. Du kannst die in deinem GitHub-Dashboard eingestellten Stellenangebote ansehen.
|
||||
|
||||
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
2. Wähle **Für Einstellung verfügbar** unter „Stellenprofil“ aus, und klicke dann auf **Stellenprofil speichern**.
|
||||
|
||||
@@ -0,0 +1,59 @@
|
||||
---
|
||||
title: Informationen zur Organisationsmitgliedschaft
|
||||
intro: 'Du kannst Mitglied einer Organisation werden, um mit Mitarbeitern oder Open-Source-Mitwirkenden in vielen Repositorys gleichzeitig zusammenzuarbeiten.'
|
||||
redirect_from:
|
||||
- /articles/about-organization-membership
|
||||
- /github/setting-up-and-managing-your-github-user-account/about-organization-membership
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Organization membership
|
||||
ms.openlocfilehash: be1f2901ed18c98edf5e05c453dec5d3c443955f
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145165049'
|
||||
---
|
||||
Ein Organisationsinhaber kann Dich einladen, seiner Organisation als Mitglied, Abrechnungsmanager oder Inhaber beizutreten. Ein Organisationsinhaber oder Mitglied mit Administratorberechtigungen für ein Repository kann Dich einladen, als externer Mitarbeiter in einem oder mehreren Repositorys zusammenzuarbeiten. Weitere Informationen findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization).
|
||||
|
||||
Auf Deiner Profilseite kannst Du auf Organisationen zugreifen, denen Du angehörst. Weitere Informationen findest du unter [Zugreifen auf eine Organisation](/articles/accessing-an-organization).
|
||||
|
||||
Wenn Du eine Einladung annimmst, einer Organisation beizutreten, können die Inhaber der Organisation unter Umständen Folgendes sehen:
|
||||
|
||||
- Deine öffentlichen Profilinformationen
|
||||
- Ihre E-Mail-Adresse
|
||||
- Ob die Zwei-Faktor-Authentifizierung bei Dir aktiviert hast
|
||||
- Repositorys, auf die Du innerhalb der Organisation Zugriff hast, und Deine Zugriffsebene
|
||||
- Bestimmte Aktivitäten innerhalb der Organisation
|
||||
- Das Land der Antragstellung
|
||||
- Deine IP-Adresse
|
||||
|
||||
Weitere Informationen findest du in den <a href="/articles/github-privacy-statement/" class="dotcom-only">Datenschutzbestimmungen von {% data variables.product.prodname_dotcom %}</a>.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Hinweis:** Inhaber*innen können die IP-Adressen der Mitglieder nicht im Auditprotokoll der Organisation anzeigen. Bei einem Sicherheitsvorfall, beispielsweise einer Kontokompromittierung oder einer versehentlichen Weitergabe vertraulicher Daten, können Unternehmensinhaber Details zum Zugriff auf private Repositorys anfordern. Zu den von uns übermittelten Informationen kann auch Deine IP-Adresse gehören.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Die Sichtbarkeit Deiner Mitgliedschaft in einer Organisation ist standardmäßig auf privat eingestellt. Du kannst wählen, ob Du einzelne Mitgliedschaften in Organisationen in Deinem Profil veröffentlichen möchtest. Weitere Informationen findest du unter [Veröffentlichen oder Ausblenden der Organisationsmitgliedschaft](/articles/publicizing-or-hiding-organization-membership).
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
Wenn Deine Organisation zu einem Enterprise-Konto gehört, bist Du automatisch Mitglied des Enterprise-Kontos und für Inhaber des Enterprise-Kontos sichtbar. Weitere Informationen findest du unter [Informationen zu Unternehmenskonten](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %} in der Dokumentation zu {% data variables.product.prodname_ghe_cloud %}.{% else %}.{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
Du kannst eine Organisation jederzeit verlassen. Weitere Informationen findest du unter [Entfernen der eigenen Person aus einer Organisation](/articles/removing-yourself-from-an-organization).
|
||||
|
||||
## Weiterführende Themen
|
||||
|
||||
- "[Informationen zu Organisationen](/articles/about-organizations)"
|
||||
- [Verwalten deiner Mitgliedschaft in Organisationen](/articles/managing-your-membership-in-organizations)
|
||||
@@ -0,0 +1,32 @@
|
||||
---
|
||||
title: Auf eine Organisation zugreifen
|
||||
intro: 'Um auf eine Organisation zuzugreifen, deren Mitglied du bist, musst du dich in deinem persönlichen Konto anmelden.'
|
||||
redirect_from:
|
||||
- /articles/error-cannot-log-in-that-account-is-an-organization
|
||||
- /articles/cannot-log-in-that-account-is-an-organization
|
||||
- /articles/how-do-i-access-my-organization-account
|
||||
- /articles/accessing-an-organization
|
||||
- /github/setting-up-and-managing-your-github-user-account/accessing-an-organization
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
ms.openlocfilehash: 3c2e98d1b28d347ba901b6d0feed15aa54c7609c
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145164933'
|
||||
---
|
||||
{% tip %}
|
||||
|
||||
**Tipp:** Nur Organisationsbesitzer können die Kontoeinstellungen für eine Organisation einsehen und ändern.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %}
|
||||
@@ -0,0 +1,33 @@
|
||||
---
|
||||
title: Ihre Mitgliedschaft in Organisationen verwalten
|
||||
intro: |-
|
||||
Wenn du Mitglied einer Organisation bist, kannst du deine Mitgliedschaft veröffentlichen oder ausblenden, die Rollen anderer Benutzer anzeigen und
|
||||
dich selbst aus der Organisation entfernen.
|
||||
redirect_from:
|
||||
- /articles/managing-your-membership-in-organizations
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
children:
|
||||
- /about-organization-membership
|
||||
- /accessing-an-organization
|
||||
- /viewing-peoples-roles-in-an-organization
|
||||
- /requesting-organization-approval-for-oauth-apps
|
||||
- /publicizing-or-hiding-organization-membership
|
||||
- /managing-your-scheduled-reminders
|
||||
- /removing-yourself-from-an-organization
|
||||
shortTitle: Manage organization membership
|
||||
ms.openlocfilehash: 6cd19e2321d928b73942d99f46a48b0501d813fb
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145164813'
|
||||
---
|
||||
|
||||
@@ -0,0 +1,54 @@
|
||||
---
|
||||
title: Verwalten Deiner geplanten Erinnerungen
|
||||
intro: 'Du kannst in Slack Erinnerungen erhalten, wenn für Dich oder Dein Team Pull Requests auf einen Review warten.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders
|
||||
shortTitle: Manage scheduled reminders
|
||||
ms.openlocfilehash: 7dab3826b1791d3b06b3a2594c3ba132c6d675b4
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145164897'
|
||||
---
|
||||
## Über geplante Erinnerungen für Benutzer
|
||||
|
||||
Geplante Erinnerungen werden verwendet, um sicherzustellen, dass Benutzer sich auf die wichtigsten Review-Anforderungen konzentrieren, die ihre Aufmerksamkeit erfordern. Geplante Erinnerungen für Pull Requests senden Dir in Slack eine Nachricht mit offenen Pull Requests, die Deinen Review zu einem bestimmten Zeitpunkt benötigen. Du kannst beispielsweise planmäßige Erinnerungen so einrichten, dass sie Dir jeden Morgen um 10 Uhr eine Nachricht in Slack zusenden über Pull Requests, die von Dir oder einem Deiner Teams überprüft werden müssen.
|
||||
|
||||
Für bestimmte Ereignisse kannst Du auch Echtzeit-Alarmierung für geplante Erinnerungen einrichten. Echtzeit-Alarme werden in Deinen Slack-Kanal gesendet, sobald ein wichtiges Ereignis stattfindet, beispielsweise wenn Du einem Review zugewiesen wirst.
|
||||
|
||||
Du kannst geplante Erinnerungen für persönliche oder für Team-Review-Anfragen für Pull Requests in Organisationen festlegen, in denen Du Mitglied bist. Bevor Du eine geplante Erinnerung für Dich selbst erstellen kannst, muss ein Organisationsinhaber Deinen Slack-Arbeitsbereich autorisieren. Weitere Informationen findest du unter [Verwalten geplanter Erinnerungen für deine Organisation](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization).
|
||||
|
||||
{% data reusables.reminders.scheduled-reminders-limitations %}
|
||||
|
||||
## Erstellen geplanter Erinnerungen für dein persönliches Konto
|
||||
|
||||
{% data reusables.user-settings.access_settings %} {% data reusables.reminders.scheduled-reminders %}
|
||||
1. Klicke neben der Organisation, für die du Erinnerungen planen möchtest, auf **Bearbeiten**.
|
||||
 {% data reusables.reminders.add-reminder %} {% data reusables.reminders.authorize-slack %} {% data reusables.reminders.days-dropdown %} {% data reusables.reminders.times-dropdowns %}
|
||||
8. Um geplante Erinnerungen für Reviews zu erhalten, die dir zugewiesen wurden, kannst du optional **Dir zugewiesene Reviewaufträge** auswählen.
|
||||
|
||||
9. Um geplante Erinnerungen für Reviews zu erhalten, die einem Team zugewiesen wurden, dem du angehörst, kannst du optional **Deinem Team zugewiesene Reviewaufträge** auswählen.
|
||||
 {% data reusables.reminders.real-time-alerts %}  {% data reusables.reminders.create-reminder %}
|
||||
|
||||
## Erstellen geplanter Erinnerungen für dein persönliches Konto
|
||||
{% data reusables.user-settings.access_settings %} {% data reusables.reminders.scheduled-reminders %}
|
||||
1. Klicke neben der Organisation, für die du geplante Erinnerungen bearbeiten möchtest, auf **Bearbeiten**.
|
||||
 {% data reusables.reminders.edit-page %} {% data reusables.reminders.update-buttons %}
|
||||
|
||||
## Löschen geplanter Erinnerungen für dein persönliches Konto
|
||||
{% data reusables.user-settings.access_settings %} {% data reusables.reminders.scheduled-reminders %}
|
||||
1. Klicke neben der Organisation, für die du Erinnerungen löschen möchtest, auf **Bearbeiten**.
|
||||
 {% data reusables.reminders.delete %}
|
||||
|
||||
## Weiterführende Themen
|
||||
|
||||
- [Verwalten geplanter Erinnerungen für deine Organisation](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)
|
||||
- [Verwalten geplanter Erinnerungen für dein Team](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team)
|
||||
@@ -0,0 +1,35 @@
|
||||
---
|
||||
title: Mitgliedschaft in einer Organisation veröffentlichen oder ausblenden
|
||||
intro: 'Wenn du öffentlich mitteilen möchtest, zu welchen Organisationen du gehörst, kannst du die Avatare der Organisationen in deinem Profil anzeigen.'
|
||||
redirect_from:
|
||||
- /articles/publicizing-or-concealing-organization-membership
|
||||
- /articles/publicizing-or-hiding-organization-membership
|
||||
- /github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Show or hide membership
|
||||
ms.openlocfilehash: 89f9c7ee5cae6215412fd20dc0590f4f8dc5bf0b
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '147881179'
|
||||
---
|
||||
|
||||
|
||||
## Sichtbarkeit Deiner Organisationsmitgliedschaft ändern
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %}
|
||||
4. Suche in der Liste der Mitglieder Deinen Benutzernamen. Wenn die Liste sehr umfangreich ist, kannst Du Deinen Benutzernamen über das Suchfeld finden.
|
||||
|
||||
5. Wähle im Menü rechts neben Deinem Benutzernamen eine neue Option für die Sichtbarkeit aus:
|
||||
- Um deine Mitgliedschaft zu veröffentlichen, wähle **Öffentlich** aus.
|
||||
- Um deine Mitgliedschaft auszublenden, wähle **Privat** aus.
|
||||
|
||||
@@ -0,0 +1,34 @@
|
||||
---
|
||||
title: Removing yourself from an organization
|
||||
intro: 'If you''re an outside collaborator or a member of an organization, you can leave the organization at any time.'
|
||||
redirect_from:
|
||||
- /articles/how-do-i-remove-myself-from-an-organization
|
||||
- /articles/removing-yourself-from-an-organization
|
||||
- /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Leave an organization
|
||||
---
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** If you're currently responsible for paying for {% data variables.product.product_name %} in your organization, removing yourself from the organization **does not** update the billing information on file for the organization. If you are currently responsible for billing, **you must** have another owner or billing manager for the organization [update the organization's payment method](/articles/adding-or-editing-a-payment-method).
|
||||
|
||||
For more information, see "[Transferring organization ownership](/articles/transferring-organization-ownership)."
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.organizations %}
|
||||
3. Under "Organizations", find the organization you'd like to remove yourself from, then click **Leave**.
|
||||
|
||||
@@ -0,0 +1,37 @@
|
||||
---
|
||||
title: Requesting organization approval for OAuth Apps
|
||||
intro: 'Organization members and outside collaborators can request that an owner approve access to organization resources for {% data variables.product.prodname_oauth_apps %}.'
|
||||
redirect_from:
|
||||
- /articles/requesting-organization-approval-for-third-party-applications
|
||||
- /articles/requesting-organization-approval-for-your-authorized-applications
|
||||
- /articles/requesting-organization-approval-for-oauth-apps
|
||||
- /github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Request OAuth App approval
|
||||
---
|
||||
|
||||
## About requesting organization approval for an {% data variables.product.prodname_oauth_app %}
|
||||
|
||||
Organization members can always request owner approval for {% data variables.product.prodname_oauth_apps %} they'd like to use, and organization owners receive a notification of pending requests.{% ifversion limit-app-access-requests %} Outside collaborators can request owner approval for {% data variables.product.prodname_oauth_apps %} they'd like to use if integration access requests are enabled. For more information, see "[Limiting OAuth App and GitHub App access requests](/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests)."{% endif %}
|
||||
|
||||
## Requesting organization approval for an {% data variables.product.prodname_oauth_app %} you've already authorized for your personal account
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.access_applications %}
|
||||
{% data reusables.user-settings.access_authorized_oauth_apps %}
|
||||
3. In the list of applications, click the name of the {% data variables.product.prodname_oauth_app %} you'd like to request access for.
|
||||
|
||||
4. Next to the organization you'd like the {% data variables.product.prodname_oauth_app %} to access, click **Request access**.
|
||||
|
||||
5. After you review the information about requesting {% data variables.product.prodname_oauth_app %} access, click **Request approval from owners**.
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)"
|
||||
@@ -0,0 +1,68 @@
|
||||
---
|
||||
title: Rollen von Personen in einer Organisation anzeigen
|
||||
intro: 'Du kannst eine Liste der Personen in deiner Organisation anzeigen und nach deren Rollen filtern. Weitere Informationen zu Organisationsrollen findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization).'
|
||||
permissions: Organization members can see people's roles in the organization.
|
||||
redirect_from:
|
||||
- /articles/viewing-people-s-roles-in-an-organization
|
||||
- /articles/viewing-peoples-roles-in-an-organization
|
||||
- /github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: View people in an organization
|
||||
ms.openlocfilehash: e0632ffeb394615b7b64ad55673b69fc738bca27
|
||||
ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/12/2022
|
||||
ms.locfileid: '146179631'
|
||||
---
|
||||
## Anzeigen von Organisationsrollen
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %}
|
||||
4. Es wird eine Liste der Personen in deiner Organisation angezeigt. Wenn du die Liste nach Rollen filtern möchtest, klicke auf **Rolle**, und wähle die gesuchte Rolle aus.
|
||||
|
||||
|
||||
{% ifversion fpt %}
|
||||
|
||||
Wenn deine Organisation {% data variables.product.prodname_ghe_cloud %} nutzt, kannst du auch die Unternehmensbesitzer*innen anzeigen, die Abrechnungseinstellungen und Richtlinien für alle Organisationen deines Unternehmens verwalten. Weitere Informationen findest du unter [Dokumentation zu {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization#view-enterprise-owners-and-their-roles-in-an-organization).
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion enterprise-owners-visible-for-org-members %}
|
||||
## Anzeigen von Unternehmensbesitzer*innen und deren Rollen in einer Organisation
|
||||
|
||||
Wenn deine Organisation über ein Unternehmenskonto verwaltet wird, kannst du die Unternehmensbesitzer*innen anzeigen, die die Abrechnungseinstellungen und Richtlinien für alle Organisationen deines Unternehmens verwalten. Weitere Informationen zu Unternehmenskonten findest du unter [Arten von {% data variables.product.prodname_dotcom %}-Konten](/get-started/learning-about-github/types-of-github-accounts).
|
||||
|
||||
Du kannst auch anzeigen, ob ein*e Unternehmensbesitzer*in eine bestimme Rolle in der Organisation innehat. Unternehmensbesitzer*innen können auch Organisationsmitglieder sein, eine andere Organisationsrolle innehaben oder von der Organisation unabhängig sein.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Hinweis:** Wenn du ein*e Organisationsbesitzer*in bist, kannst du auch Unternehmensbesitzer*innen dazu einladen, eine Rolle in der Organisation zu übernehmen. Wenn ein*e Unternehmensbesitzer*in die Einladung annimmt, wird ein Sitz oder eine Lizenz in der Organisation von den verfügbaren Lizenzen deines Unternehmens verwendet. Weitere Informationen zur Funktionsweise von Lizenzierungen findest du unter [Rollen in einem Unternehmen](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
| **Unternehmensrolle** | **Organisationsrolle** | **Zugriff auf die Organisation und Auswirkungen** |
|
||||
|----|----|----|----|
|
||||
| Enterprise-Inhaber | Unabhängig oder keine offizielle Organisationsrolle | Diese Rolle kann nicht auf Inhalte oder Repositorys der Organisation zugreifen, verwaltet jedoch Unternehmenseinstellungen und Richtlinien, die sich auf deine Organisation auswirken. |
|
||||
| Enterprise-Inhaber | Organisationsbesitzer | Diese Rolle kann Organisationseinstellungen konfigurieren und den Zugriff auf die Ressourcen der Organisation durch Teams usw. verwalten. |
|
||||
| Enterprise-Inhaber | Organisationsmitglied | Diese Rolle kann auf Ressourcen und Inhalte der Organisation (z. B. Repositorys) zugreifen, hat jedoch keinen Zugriff auf die Einstellungen der Organisation. |
|
||||
|
||||
Informationen zum Anzeigen aller Rollen in einer Organisation findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization). {% ifversion custom-repository-roles %} Ein Organisationsmitglied kann auch über eine benutzerdefinierte Rolle für ein bestimmtes Repository verfügen. Weitere Informationen findest du unter [Verwalten benutzerdefinierter Repositoryrollen für eine Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}
|
||||
|
||||
Weitere Informationen zur Rolle „Unternehmensbesitzer“ findest du unter [Rollen in einem Unternehmen](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner).
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %}
|
||||
4. Klicke in der linken Randleiste unter „Unternehmensberechtigungen“ auf **Unternehmensbesitzer**.
|
||||
|
||||
5. Zeige die Liste der Unternehmensbesitzer*innen deines Unternehmens an. Wenn der*die Unternehmensbesitzer*in ebenfalls Mitglied deiner Organisation ist, kannst du die Rolle in der Organisation anzeigen.
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: Best practices for leaving your company
|
||||
intro: 'If you use your account on {% data variables.product.product_name %} for both personal and work purposes, there are a few things to keep in mind when you leave your company or organization.'
|
||||
redirect_from:
|
||||
- /articles/best-practices-for-leaving-your-company
|
||||
- /github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company
|
||||
- /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Leaving your company
|
||||
---
|
||||
|
||||
Before you leave your company, make sure you update the following information in your personal account:
|
||||
|
||||
- Unverify your company email address by [deleting it in your Email settings](/articles/changing-your-primary-email-address). You can then re-add it without verifying to keep any associated commits linked to your account.
|
||||
- [Change your primary email address](/articles/changing-your-primary-email-address) from your company email to your personal email.
|
||||
- [Verify your new primary email address](/articles/verifying-your-email-address).
|
||||
- [Change your GitHub username](/articles/changing-your-github-username) to remove any references to your company or organization, if necessary.
|
||||
- If you've enabled two-factor (2FA) authentication for your personal account, make sure that you (not your company) control the 2FA authentication method you have configured. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)."
|
||||
|
||||
## Leaving organizations
|
||||
|
||||
If you've been working with repositories that belong to an organization, you'll want to [remove yourself as a member of the organization](/articles/removing-yourself-from-an-organization). Note that if you are the organization owner, you should first [transfer ownership of the organization](/articles/transferring-organization-ownership) to another person.
|
||||
|
||||
Unless you're using a {% data variables.enterprise.prodname_managed_user %}, you'll still be able to access your personal account, even after leaving the organization. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}]({% ifversion not ghec%}/enterprise-cloud@latest{% endif %}/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
|
||||
## Removing professional associations with personal repositories
|
||||
|
||||
If you've been collaborating professionally with another person on repositories that belong to their personal account, you'll want to [remove yourself as a collaborator](/articles/removing-yourself-from-a-collaborator-s-repository) from those repositories.
|
||||
|
||||
- [Stop watching repositories](https://github.com/watching) related to your work. You won't want those notifications anymore!
|
||||
- [Transfer repositories you own](/articles/how-to-transfer-a-repository) that others may need to continue working on after you leave.
|
||||
- [Delete forks that belong to you](/articles/deleting-a-repository) that are related to the work you were doing. Don't worry, deleting a fork doesn't delete the upstream repository.
|
||||
- Delete local copies of your forks that may exist on your computer:
|
||||
|
||||
```shell
|
||||
$ rm -rf WORK_DIRECTORY
|
||||
```
|
||||
@@ -0,0 +1,74 @@
|
||||
---
|
||||
title: Converting a user into an organization
|
||||
redirect_from:
|
||||
- /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization
|
||||
- /articles/explaining-the-account-transformation-warning
|
||||
- /articles/converting-a-user-into-an-organization
|
||||
- /github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
|
||||
- /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization
|
||||
intro: You can convert your personal account into an organization. This allows more granular permissions for repositories that belong to the organization.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: User into an organization
|
||||
---
|
||||
{% warning %}
|
||||
|
||||
**Warning**: Before converting a user into an organization, keep these points in mind.
|
||||
|
||||
* You will **no longer** be able to sign into the converted personal account.
|
||||
* You will **no longer** be able to create or modify gists owned by the converted personal account.
|
||||
* An organization **cannot** be converted back to a user.
|
||||
* The SSH keys, OAuth tokens, job profile, reactions, and associated user information, **will not** be transferred to the organization. This is only true for the personal account that's being converted, not any of the personal account's collaborators.
|
||||
* Any {% data variables.product.prodname_github_apps %} installed on the converted personal account will be uninstalled.
|
||||
* Any commits made with the converted personal account **will no longer be linked** to that account. The commits themselves **will** remain intact.
|
||||
* Any existing comments made by the converted personal account **will no longer be linked** to that account. The comments themselves **will** remain intact, but will be associated with the `ghost` user.
|
||||
* Any forks of private repositories made with the converted personal account will be deleted.
|
||||
{% endwarning %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
## Keep your personal account and create a new organization manually
|
||||
|
||||
If you want your organization to have the same name that you are currently using for your personal account, or if you want to keep your personal account's information intact, then you must create a new organization and transfer your repositories to it instead of converting your personal account into an organization.
|
||||
|
||||
1. To retain your current personal account name for your personal use, [change the name of your personal account](/articles/changing-your-github-username) to something new and wonderful.
|
||||
2. [Create a new organization](/articles/creating-a-new-organization-from-scratch) with the original name of your personal account.
|
||||
3. [Transfer your repositories](/articles/transferring-a-repository) to your new organization account.{% endif %}
|
||||
|
||||
## Convert your personal account into an organization automatically
|
||||
|
||||
You can also convert your personal account directly into an organization. Converting your account:
|
||||
- Preserves the repositories as they are without the need to transfer them to another account manually
|
||||
- Automatically invites collaborators to teams with permissions equivalent to what they had before
|
||||
{% ifversion fpt or ghec %}- For personal accounts on {% data variables.product.prodname_pro %}, automatically transitions billing to [the paid {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts) without the need to re-enter payment information, adjust your billing cycle, or double pay at any time{% endif %}
|
||||
|
||||
1. Create a new personal account, which you'll use to sign into GitHub and access the organization and your repositories after you convert.
|
||||
2. [Leave any organizations](/articles/removing-yourself-from-an-organization) the personal account you're converting has joined.
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.organizations %}
|
||||
5. Under "Transform account", click **Turn <username> into an organization**.
|
||||
|
||||
6. In the Account Transformation Warning dialog box, review and confirm the conversion. Note that the information in this box is the same as the warning at the top of this article.
|
||||
|
||||
7. On the "Transform your user into an organization" page, under "Choose an organization owner", choose either the secondary personal account you created in the previous section or another user you trust to manage the organization.
|
||||
|
||||
8. Choose your new organization's subscription and enter your billing information if prompted.
|
||||
9. Click **Create Organization**.
|
||||
10. Sign in to the new personal account you created in step one, then use the context switcher to access your new organization.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip**: When you convert a personal account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as *outside collaborators*. You can then invite *outside collaborators* to become members of your new organization if you wish. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## Further reading
|
||||
- "[Setting up teams](/articles/setting-up-teams)"
|
||||
{% ifversion fpt or ghec %}- "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)"{% endif %}
|
||||
- "[Accessing an organization](/articles/accessing-an-organization)"
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
title: Deleting your personal account
|
||||
intro: 'You can delete your personal account on {% data variables.location.product_location %} at any time.'
|
||||
redirect_from:
|
||||
- /articles/deleting-a-user-account
|
||||
- /articles/deleting-your-user-account
|
||||
- /github/setting-up-and-managing-your-github-user-account/deleting-your-user-account
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account
|
||||
- /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Delete your account
|
||||
---
|
||||
|
||||
## About deletion of your personal account
|
||||
|
||||
Deleting your personal account removes all repositories, forks of private repositories, wikis, issues, pull requests, and pages owned by your account. {% ifversion fpt or ghec %}Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted. Your resources and comments will become associated with the [ghost user](https://github.com/ghost).{% else %}Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted.{% endif %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: If your enterprise manages your account and you sign into {% data variables.location.product_location %} through your company's identity provider (IdP), you cannot delete your account. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}When you delete your account we stop billing you. The email address associated with the account becomes available for use with a different account on {% data variables.location.product_location %}. After 90 days, the account name also becomes available to anyone else to use on a new account. {% endif %}
|
||||
|
||||
If you're the only owner of an organization, you must transfer ownership to another person or delete the organization before you can delete your personal account. If there are other owners in the organization, you must remove yourself from the organization before you can delete your personal account.
|
||||
|
||||
For more information, see the following articles.
|
||||
|
||||
- "[Transferring organization ownership](/articles/transferring-organization-ownership)"
|
||||
- "[Deleting an organization account](/articles/deleting-an-organization-account)"
|
||||
- "[Removing yourself from an organization](/articles/removing-yourself-from-an-organization/)"
|
||||
|
||||
## Back up your account data
|
||||
|
||||
Before you delete your personal account, make a copy of all repositories, private forks, wikis, issues, and pull requests owned by your account. For more information, see "[Backing up a repository](/repositories/archiving-a-github-repository/backing-up-a-repository)."
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** Once your personal account has been deleted, {% ifversion fpt or ghec %}{% data variables.product.company_short %}{% elsif ghes or ghae %}an enterprise owner{% endif %} cannot restore your content.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
## Delete your personal account
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.account_settings %}
|
||||
3. At the bottom of the Account Settings page, under "Delete account", click **Delete your account**. Before you can delete your personal account:
|
||||
- If you're the only owner in the organization, you must transfer ownership to another person or delete your organization.
|
||||
- If there are other organization owners in the organization, you must remove yourself from the organization.
|
||||
|
||||
4. In the "Make sure you want to do this" dialog box, complete the steps to confirm you understand what happens when your account is deleted:
|
||||
|
||||
{% ifversion fpt or ghec %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and {% data variables.product.prodname_pages %} sites owned by your account will be deleted and your billing will end immediately, and your username will be available to anyone for use on {% data variables.product.product_name %} after 90 days.
|
||||
{% else %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and pages owned by your account will be deleted, and your username will be available for use on {% data variables.product.product_name %}.
|
||||
{% endif %}- In the first field, type your {% data variables.product.product_name %} username or email.
|
||||
- In the second field, type the phrase from the prompt.
|
||||
@@ -0,0 +1,19 @@
|
||||
---
|
||||
title: Managing your personal account
|
||||
intro: 'You can manage your personal account on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. For example, you can {% ifversion fpt or ghec %}manage multiple accounts, {% endif %}convert an account to an organization{% ifversion fpt or ghec or ghes %}, or delete an account{% endif %}.'
|
||||
shortTitle: Manage personal account
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
children:
|
||||
- /managing-multiple-accounts
|
||||
- /merging-multiple-personal-accounts
|
||||
- /converting-a-user-into-an-organization
|
||||
- /best-practices-for-leaving-your-company
|
||||
- /deleting-your-personal-account
|
||||
---
|
||||
|
||||
@@ -0,0 +1,105 @@
|
||||
---
|
||||
title: Managing multiple accounts
|
||||
intro: 'If you use one workstation to contribute to projects for more than one account on {% data variables.location.product_location %}, you can modify your Git configuration to simplify the contribution process.'
|
||||
versions:
|
||||
feature: multiple-accounts-one-workstation
|
||||
topics:
|
||||
- Accounts
|
||||
- Git
|
||||
- GitHub
|
||||
shortTitle: Manage multiple accounts
|
||||
---
|
||||
|
||||
## About management of multiple accounts
|
||||
|
||||
In some cases, you may need to use multiple accounts on {% data variables.location.product_location %}. For example, you may have a personal account for open source contributions, and your employer may also create and manage a user account for you within an enterprise.
|
||||
|
||||
You cannot use your {% data variables.enterprise.prodname_managed_user %} to contribute to public projects on {% data variables.location.product_location %}, so you must contribute to those resources using your personal account. For more information, see "[About {% data variables.product.prodname_emus %}]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-user-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% elsif ghec %}."{% endif %}
|
||||
|
||||
If you want to use one workstation to contribute from both accounts, you can simplify contribution with Git by using a mixture of protocols to access repository data, or by using credentials on a per-repository basis.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: Be mindful when you use one workstation to contribute to two separate accounts. Management of two or more accounts can increase the chance of mistakenly leaking internal code to the public.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
If you aren't required to use a {% data variables.enterprise.prodname_managed_user %}, {% data variables.product.company_short %} recommends that you use one personal account for all your work on {% data variables.location.product_location %}. With a single personal account, you can contribute to a combination of personal, open source, or professional projects using one identity. Other people can invite the account to contribute to both individual repositories and repositories owned by an organization, and the account can be a member of multiple organizations or enterprises.
|
||||
|
||||
## Contributing to two accounts using HTTPS and SSH
|
||||
|
||||
If you contribute with two accounts from one workstation, you can access repositories by using a different protocol and credentials for each account.
|
||||
|
||||
Git can use either the HTTPS or SSH protocol to access and update data in repositories on {% data variables.location.product_location %}. The protocol you use to clone a repository determines which credentials your workstation will use to authenticate when you access the repository. With this approach to account management, you store the credentials for one account to use for HTTPS connections and upload an SSH key to the other account to use for SSH connections.
|
||||
|
||||
You can find both the HTTPS or an SSH URLs for cloning a repository on {% data variables.product.product_name %}. For more information, see "[Cloning a repository](/repositories/creating-and-managing-repositories/cloning-a-repository)."
|
||||
|
||||
For more information about the use of SSH to access repositories on {% data variables.product.product_name %}, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/authentication/connecting-to-github-with-ssh)."
|
||||
|
||||
## Contributing to multiple accounts using HTTPS and {% data variables.product.pat_generic %}s
|
||||
|
||||
Alternatively, if you want to use the HTTPS protocol for both accounts, you can use different {% data variables.product.pat_generic %}s for each account by configuring Git to store different credentials for each repository.
|
||||
|
||||
{% mac %}
|
||||
|
||||
{% data reusables.git.open-terminal %}
|
||||
{% data reusables.git.confirm-credential-manager %}
|
||||
{% data reusables.git.clear-the-stored-credentials %}
|
||||
{% data reusables.git.no-credential-manager %}
|
||||
- If the output is `osxkeychain`, you're using the macOS keychain. To clear the credentials, enter the following command.
|
||||
|
||||
```shell{:copy}
|
||||
git credential-osxkeychain erase https://github.com
|
||||
```
|
||||
{% data reusables.git.clear-stored-gcm-credentials %}
|
||||
{% data reusables.git.cache-on-repository-path %}
|
||||
{% data reusables.accounts.create-personal-access-tokens %}
|
||||
{% data reusables.git.provide-credentials %}
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
1. Open Git Bash.
|
||||
{% data reusables.git.confirm-credential-manager %}
|
||||
{% data reusables.git.clear-the-stored-credentials %}
|
||||
{% data reusables.git.no-credential-manager %}
|
||||
{% data reusables.git.clear-stored-gcm-credentials %}
|
||||
- If the output is `wincred`, you're using the Windows Credential Manager. To clear the credentials, enter the following command.
|
||||
|
||||
```shell{:copy}
|
||||
cmdkey /delete:LegacyGeneric:target=git:https://github.com
|
||||
```
|
||||
{% data reusables.git.cache-on-repository-path %}
|
||||
{% data reusables.accounts.create-personal-access-tokens %}
|
||||
{% data reusables.git.provide-credentials %}
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
{% linux %}
|
||||
|
||||
{% data reusables.git.open-terminal %}
|
||||
{% data reusables.git.confirm-credential-manager %}
|
||||
{% data reusables.git.clear-the-stored-credentials %}
|
||||
{% data reusables.git.no-credential-manager %}
|
||||
{% data reusables.git.clear-stored-gcm-credentials %}
|
||||
{% data reusables.git.cache-on-repository-path %}
|
||||
{% data reusables.accounts.create-personal-access-tokens %}
|
||||
{% data reusables.git.provide-credentials %}
|
||||
|
||||
{% endlinux %}
|
||||
|
||||
## Contributing to multiple accounts using SSH and `GIT_SSH_COMMAND`
|
||||
|
||||
If you want to use the SSH protocol for both accounts, you can use different SSH keys for each account. For more information about using SSH, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/authentication/connecting-to-github-with-ssh)."
|
||||
|
||||
To use a different SSH key for different repositories that you clone to your workstation, you must write a shell wrapper function for Git operations. The function should perform the following steps.
|
||||
1. Determine the repository's full name with owner, using a command such as `git config --get remote.origin.url`.
|
||||
2. Choose the correct SSH key for authentication.
|
||||
3. Modify `GIT_SSH_COMMAND` accordingly. For more information about `GIT_SSH_COMMAND`, see [Environment Variables](https://git-scm.com/docs/git#Documentation/git.txt-codeGITSSHCOMMANDcode) in the Git documentation.
|
||||
|
||||
For example, the following command sets the `GIT_SSH_COMMAND` environment variable to specify an SSH command that uses the private key file at **_PATH/TO/KEY/FILE_** for authentication to clone the repository named **_OWNER_**/**_REPOSITORY_** on {% data variables.location.product_location %}.
|
||||
|
||||
<pre>
|
||||
GIT_SSH_COMMAND='ssh -i <em>PATH/TO/KEY/FILE</em> -o IdentitiesOnly=yes' git clone git@github.com:<em>OWNER</em>/<em>REPOSITORY</em>
|
||||
</pre>
|
||||
@@ -0,0 +1,54 @@
|
||||
---
|
||||
title: Zusammenführen mehrerer persönlicher Konten
|
||||
intro: 'Wenn du separate Konten für die Arbeit und für die private Nutzung besitzt, kannst du die Konten zusammenführen.'
|
||||
redirect_from:
|
||||
- /articles/can-i-merge-two-accounts
|
||||
- /articles/keeping-work-and-personal-repositories-separate
|
||||
- /articles/merging-multiple-user-accounts
|
||||
- /github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts
|
||||
- /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Merge multiple accounts
|
||||
ms.openlocfilehash: 39198c8fdd0078321774eac4180f84a2b039d25e
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147687167'
|
||||
---
|
||||
{% tip %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
**Tipp:** {% data variables.product.prodname_emus %} ermöglichen es einem Unternehmen, eindeutige persönliche Konten für seine Mitglieder über einen Identitätsanbieter (IdP) bereitzustellen. Weitere Informationen findest du unter [Informationen zu Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users). Für andere Anwendungsfälle wird empfohlen, nur ein Benutzerkonto für die Verwaltung persönlicher und beruflicher Repositorys zu verwenden.
|
||||
|
||||
{% else %}
|
||||
|
||||
**Tipp:** Es wird empfohlen, nur ein Benutzerkonto für die Verwaltung persönlicher und beruflicher Repositorys zu verwenden.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warnung:**
|
||||
- Organisations- und Repositoryzugriffsberechtigungen können nicht zwischen Konten übertragen werden. Wenn das Konto, das Du löschen möchtest, über eine vorhandene Zugriffsberechtigung verfügt, muss ein Organisationsbesitzer oder Repositoryadministrator das Konto einladen, das Du beibehalten möchtest.
|
||||
- Alle Commits, die mit einer über GitHub bereitgestellten `noreply`-E-Mail-Adresse erstellt wurden, können nicht von einem Konto in ein anderes übertragen werden. Wenn für das Konto, das du löschen möchtest, die Option **"Keep my email address private"** (Meine E-Mail-Adresse privat halten) verwendet wird, ist es nicht möglich, die von dem Konto erstellten Commits an das Konto zu übertragen, das Du behalten möchtest.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
1. [Übertrage alle Repositorys](/articles/how-to-transfer-a-repository) aus dem Konto, das Du löschen möchtest, in das Konto, das Du behalten möchtest. Issues, Pull Requests und Wikis werden ebenfalls übertragen. Überprüfe, ob die Repositorys in dem Konto, das Du behalten möchtest, vorhanden sind.
|
||||
2. [Aktualisiere die Remote-URLs](/github/getting-started-with-github/managing-remote-repositories) in allen lokalen Klonen der Repositorys, die verschoben wurden.
|
||||
3. [Lösche das Konto](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account), das Du nicht mehr verwenden möchtest.
|
||||
4. Um dem neuen Konto frühere Commits zuzuweisen, füge die E-Mail-Adresse hinzu, die Du zum Erstellen des Commits für das Konto verwendet hast, das Du beibehältst. Weitere Informationen findest du unter [Warum werden meine Beiträge nicht auf meinem Profil angezeigt?](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)
|
||||
|
||||
## Weiterführende Themen
|
||||
|
||||
- "[Unterschiedliche Arten von {% data variables.product.prodname_dotcom %}-Konten](/articles/types-of-github-accounts)"
|
||||
@@ -0,0 +1,60 @@
|
||||
---
|
||||
title: About continuous integration
|
||||
intro: 'You can create custom continuous integration (CI) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.'
|
||||
redirect_from:
|
||||
- /articles/about-continuous-integration
|
||||
- /github/automating-your-workflow-with-github-actions/about-continuous-integration
|
||||
- /actions/automating-your-workflow-with-github-actions/about-continuous-integration
|
||||
- /actions/building-and-testing-code-with-continuous-integration/about-continuous-integration
|
||||
- /actions/guides/about-continuous-integration
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: overview
|
||||
topics:
|
||||
- CI
|
||||
shortTitle: Continuous integration
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## About continuous integration
|
||||
|
||||
Continuous integration (CI) is a software practice that requires frequently committing code to a shared repository. Committing code more often detects errors sooner and reduces the amount of code a developer needs to debug when finding the source of an error. Frequent code updates also make it easier to merge changes from different members of a software development team. This is great for developers, who can spend more time writing code and less time debugging errors or resolving merge conflicts.
|
||||
|
||||
When you commit code to your repository, you can continuously build and test the code to make sure that the commit doesn't introduce errors. Your tests can include code linters (which check style formatting), security checks, code coverage, functional tests, and other custom checks.
|
||||
|
||||
Building and testing your code requires a server. You can build and test updates locally before pushing code to a repository, or you can use a CI server that checks for new code commits in a repository.
|
||||
|
||||
## About continuous integration using {% data variables.product.prodname_actions %}
|
||||
|
||||
{% ifversion ghae %}CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on runner systems that you host. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
|
||||
{% else %} CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on {% data variables.product.prodname_dotcom %}-hosted virtual machines, or on machines that you host yourself. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)."
|
||||
{% endif %}
|
||||
|
||||
You can configure your CI workflow to run when a {% data variables.product.prodname_dotcom %} event occurs (for example, when new code is pushed to your repository), on a set schedule, or when an external event occurs using the repository dispatch webhook.
|
||||
|
||||
{% data variables.product.product_name %} runs your CI tests and provides the results of each test in the pull request, so you can see whether the change in your branch introduces an error. When all CI tests in a workflow pass, the changes you pushed are ready to be reviewed by a team member or merged. When a test fails, one of your changes may have caused the failure.
|
||||
|
||||
When you set up CI in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends CI workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a starter workflow that installs your Node.js packages and runs your tests. You can use the CI starter workflow suggested by {% data variables.product.product_name %}, customize the suggested starter workflow, or create your own custom workflow file to run your CI tests.
|
||||
|
||||
|
||||
|
||||
In addition to helping you set up CI workflows for your project, you can use {% data variables.product.prodname_actions %} to create workflows across the full software development life cycle. For example, you can use actions to deploy, package, or release your project. For more information, see "[About {% data variables.product.prodname_actions %}](/articles/about-github-actions)."
|
||||
|
||||
For a definition of common terms, see "[Core concepts for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)."
|
||||
|
||||
## Starter workflow
|
||||
|
||||
{% data variables.product.product_name %} offers CI starter workflow for a variety of languages and frameworks.
|
||||
|
||||
Browse the complete list of CI starter workflow offered by {% data variables.product.company_short %} in the {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` repository on {% data variables.location.product_location %}{% endif %}.
|
||||
|
||||
## Further reading
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"
|
||||
{% endif %}
|
||||
@@ -0,0 +1,219 @@
|
||||
---
|
||||
title: Erstellen und Testen von Go
|
||||
intro: 'Du kannst einen Continuous Integration-Workflow (CI) erstellen, um dein Go-Projekt zu erstellen und zu testen.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: tutorial
|
||||
topics:
|
||||
- CI
|
||||
shortTitle: Build & test Go
|
||||
ms.openlocfilehash: 590edc2af0b7f370e52b449f320bdc2a758450bc
|
||||
ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160850'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## Einführung
|
||||
|
||||
In dieser Anleitung erfährst du, wie du ein Go-Paket erstellst, testest und veröffentlichst.
|
||||
|
||||
Von {% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} {% else %} {% data variables.product.prodname_dotcom %} gehostete Runner verfügen über einen Toolcache mit vorinstallierter Software, in dem die Abhängigkeiten von Go enthalten sind. Eine umfassende Liste mit aktueller Software und den vorinstallierten Versionen von Go findest du unter [Informationen zu von {% data variables.product.prodname_dotcom %} gehosteten Runnern](/actions/using-github-hosted-runners/about-github-hosted-runners#preinstalled-software).
|
||||
{% endif %}
|
||||
|
||||
## Voraussetzungen
|
||||
|
||||
Du solltest bereits mit der YAML-Syntax vertraut sein und wissen, wie sie mit {% data variables.product.prodname_actions %} verwendet wird. Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-syntax-for-github-actions).
|
||||
|
||||
Du solltest über grundlegende Kenntnisse in Bezug auf die Go-Programmiersprache verfügen. Weitere Informationen findest du unter [Erste Schritte mit Go](https://golang.org/doc/tutorial/getting-started).
|
||||
|
||||
## Verwenden des Go-Starterworkflows
|
||||
|
||||
{% data variables.product.prodname_dotcom %} enthält einen Go-Starterworkflow, der die für die meisten Go-Projekte funktionieren sollte. Dieser Leitfaden enthält Beispiele, die du zum Anpassen des Starterworkflows verwenden kannst. Weitere Informationen findest du im [Go-Starterworkflow](https://github.com/actions/starter-workflows/blob/main/ci/go.yml).
|
||||
|
||||
Für einen schnellen Einstieg fügst du den Starterworkflow zum Verzeichnis `.github/workflows` deines Repositorys hinzu.
|
||||
|
||||
```yaml{:copy}
|
||||
name: Go package
|
||||
|
||||
on: [push]
|
||||
|
||||
jobs:
|
||||
build:
|
||||
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
|
||||
- name: Set up Go
|
||||
uses: {% data reusables.actions.action-setup-go %}
|
||||
with:
|
||||
go-version: 1.15
|
||||
|
||||
- name: Build
|
||||
run: go build -v ./...
|
||||
|
||||
- name: Test
|
||||
run: go test -v ./...
|
||||
```
|
||||
|
||||
## Angeben einer Go-Version
|
||||
|
||||
Der einfachste Weg, eine Go-Version anzugeben, bietet die Aktion `setup-go` von {% data variables.product.prodname_dotcom %}. Weitere Informationen findest du unter der [`setup-go`-Aktion](https://github.com/actions/setup-go/).
|
||||
|
||||
Um eine vorinstallierte Version von Go auf einen von {% data variables.product.prodname_dotcom %} gehosteten Runner zu verwenden, musst du die relevante Version an die `go-version`-Eigenschaft der `setup-go`-Aktion übergeben. Mit dieser Aktion wird im Toolcache der jeweiligen Runner nach einer bestimmten Version von Go gesucht, und die erforderlichen Binärdateien werden zu `PATH` hinzugefügt. Diese Änderungen bleiben für den Rest des Auftrags beibehalten.
|
||||
|
||||
Die Aktion `setup-go` wird als Methode zur Verwendung von Go mit {% data variables.product.prodname_actions %} empfohlen, da damit ein konsistentes Verhalten bei verschiedenen Runnern und verschiedenen Version von Go gewährleistet werden kann. Wenn du einen selbstgehosteten Runner verwendest, musst du .NET installieren und zu `PATH` hinzufügen.
|
||||
|
||||
### Verwenden mehrerer Versionen von Go
|
||||
|
||||
```yaml{:copy}
|
||||
name: Go
|
||||
|
||||
on: [push]
|
||||
|
||||
jobs:
|
||||
build:
|
||||
|
||||
runs-on: ubuntu-latest
|
||||
strategy:
|
||||
matrix:
|
||||
go-version: [ '1.14', '1.15', '1.16.x' ]
|
||||
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Setup Go {% raw %}${{ matrix.go-version }}{% endraw %}
|
||||
uses: {% data reusables.actions.action-setup-go %}
|
||||
with:
|
||||
go-version: {% raw %}${{ matrix.go-version }}{% endraw %}
|
||||
# You can test your matrix by printing the current Go version
|
||||
- name: Display Go version
|
||||
run: go version
|
||||
```
|
||||
|
||||
### Verwenden einer bestimmten Version von Go
|
||||
|
||||
Du kannst einen Auftrag so konfigurieren, dass eine bestimmte Version von Go verwendet wird, z. B. `1.16.2`. Alternativ kannst du auch Syntax für semantische Versionierung verwenden, um die neuste Nebenversion abzurufen. In diesem Beispiel wird das neueste Patchrelease von Go 1.16 verwendet:
|
||||
|
||||
```yaml{:copy}
|
||||
- name: Setup Go 1.16.x
|
||||
uses: {% data reusables.actions.action-setup-go %}
|
||||
with:
|
||||
# Semantic version range syntax or exact version of Go
|
||||
go-version: '1.16.x'
|
||||
```
|
||||
|
||||
## Installieren von Abhängigkeiten
|
||||
|
||||
Du kannst `go get` zum Installieren von Abhängigkeiten verwenden:
|
||||
|
||||
```yaml{:copy}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Setup Go
|
||||
uses: {% data reusables.actions.action-setup-go %}
|
||||
with:
|
||||
go-version: '1.16.x'
|
||||
- name: Install dependencies
|
||||
run: |
|
||||
go get .
|
||||
go get example.com/octo-examplemodule
|
||||
go get example.com/octo-examplemodule@v1.3.4
|
||||
```
|
||||
|
||||
{% ifversion actions-caching %}
|
||||
|
||||
### Abhängigkeiten „cachen“ (zwischenspeichern)
|
||||
|
||||
Du kannst die Abhängigkeiten mithilfe der [Aktion `setup-go`](https://github.com/actions/setup-go) zwischenspeichern und wiederherstellen. Standardmäßig ist die Zwischenspeicherung deaktiviert, du kannst jedoch den `cache`-Parameter auf `true` festlegen, um sie zu aktivieren.
|
||||
|
||||
Wenn die Zwischenspeicherung aktiviert ist, sucht die `setup-go`-Aktion nach der Abhängigkeitsdatei `go.sum` im Repositorystamm und verwendet den Hash der Abhängigkeitsdatei als Teil des Cacheschlüssels.
|
||||
|
||||
```yaml{:copy}
|
||||
- name: Setup Go
|
||||
uses: {% data reusables.actions.action-setup-go %}
|
||||
with:
|
||||
go-version: '1.16.x'
|
||||
cache: true
|
||||
```
|
||||
|
||||
Alternativ kannst du den `cache-dependency-path`-Parameter in Fällen verwenden, in denen mehrere Abhängigkeitsdateien verwendet werden, oder wenn sie sich in verschiedenen Unterverzeichnissen befinden.
|
||||
|
||||
```yaml{:copy}
|
||||
- uses: {% data reusables.actions.action-setup-go %}
|
||||
with:
|
||||
go-version: '1.17'
|
||||
cache: true
|
||||
cache-dependency-path: subdir/go.sum
|
||||
```
|
||||
|
||||
Wenn du eine benutzerdefinierte Anforderung verwendest oder genauere Steuerungsmöglichkeiten zum Zwischenspeichern benötigst, kannst du die [Aktion `cache`](https://github.com/marketplace/actions/cache) verwendest. Weitere Informationen findest du unter [Zwischenspeichern von Abhängigkeiten zum Beschleunigen von Workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows).
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Deinen Code bauen und testen
|
||||
|
||||
Du kannst die gleichen Befehle verwenden, die du auch lokal verwendest, um deinen Code zu bauen und zu testen. In diesem Beispielworkflow wird veranschaulicht, wie die Befehle `go build` und `go test` in einem Auftrag verwendet werden:
|
||||
|
||||
```yaml{:copy}
|
||||
name: Go
|
||||
on: [push]
|
||||
|
||||
jobs:
|
||||
build:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Setup Go
|
||||
uses: {% data reusables.actions.action-setup-go %}
|
||||
with:
|
||||
go-version: '1.16.x'
|
||||
- name: Install dependencies
|
||||
run: go get .
|
||||
- name: Build
|
||||
run: go build -v ./...
|
||||
- name: Test with the Go CLI
|
||||
run: go test
|
||||
```
|
||||
|
||||
## Workflow-Daten als Artefakte paketieren
|
||||
|
||||
Nach Abschluss eines Workflows kannst du die resultierenden Artefakte für die Analyse hochladen. Zum Beispiel kann es notwendig sein, Logdateien, Core Dumps, Testergebnisse oder Screenshots zu speichern. Im folgenden Beispiel wird gezeigt, wie die Aktion `upload-artifact` zum Hochladen von Testergebnissen verwendet werden kann.
|
||||
|
||||
Weitere Informationen findest du unter [Speichern von Workflowdaten als Artefakte](/actions/using-workflows/storing-workflow-data-as-artifacts).
|
||||
|
||||
```yaml{:copy}
|
||||
name: Upload Go test results
|
||||
|
||||
on: [push]
|
||||
|
||||
jobs:
|
||||
build:
|
||||
|
||||
runs-on: ubuntu-latest
|
||||
strategy:
|
||||
matrix:
|
||||
go-version: [ '1.14', '1.15', '1.16.x' ]
|
||||
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Setup Go
|
||||
uses: {% data reusables.actions.action-setup-go %}
|
||||
with:
|
||||
go-version: {% raw %}${{ matrix.go-version }}{% endraw %}
|
||||
- name: Install dependencies
|
||||
run: go get .
|
||||
- name: Test with Go
|
||||
run: go test -json > TestResults-{% raw %}${{ matrix.go-version }}{% endraw %}.json
|
||||
- name: Upload Go test results
|
||||
uses: {% data reusables.actions.action-upload-artifact %}
|
||||
with:
|
||||
name: Go-results-{% raw %}${{ matrix.go-version }}{% endraw %}
|
||||
path: TestResults-{% raw %}${{ matrix.go-version }}{% endraw %}.json
|
||||
```
|
||||
@@ -0,0 +1,122 @@
|
||||
---
|
||||
title: Java bauen und testen mit Ant
|
||||
intro: 'Du kannst einen Workflow für kontinuierliche Integration (CI) in GitHub-Aktionen erstellen, um Dein Java-Projekt mit Ant zu bauen und zu testen.'
|
||||
redirect_from:
|
||||
- /actions/language-and-framework-guides/building-and-testing-java-with-ant
|
||||
- /actions/guides/building-and-testing-java-with-ant
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: tutorial
|
||||
topics:
|
||||
- CI
|
||||
- Java
|
||||
- Ant
|
||||
shortTitle: Build & test Java & Ant
|
||||
ms.openlocfilehash: d1e73fdce7bf23bf1b86ec3eb4d0f8acd9b6d292
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145088732'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## Einführung
|
||||
|
||||
Dieser Leitfaden zeigt Dir, wie Du einen Workflow erstellen kannst, der eine kontinuierliche Integration (CI) für Dein Java-Projekt mit Hilfe des Build-Systems Ant durchführt. Der Workflow, den Du erstellst, zeigt Dir, wenn Commits zu einem Pull-Request zu Build- oder Testfehlern für deinen Standard-Zweig führen. Dieser Ansatz kann dazu beitragen, dass Dein Code immer brauchbar ist. Du kannst Deinen CI-Workflow so erweitern, dass er Artefakte von einem Workflow-Lauf hochlädt.
|
||||
|
||||
{% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} {% else %} {% data variables.product.prodname_dotcom %}-gehostete Runner verfügen über einen Toolcache mit vorinstallierter Software, die Java Development Kits (JDKs) und Ant umfasst. Eine Liste der Software und der vorinstallierten Versionen für JDK und Ant findest du unter [Spezifikationen für {% data variables.product.prodname_dotcom %}-gehostete Runner](/actions/reference/specifications-for-github-hosted-runners/#supported-software).
|
||||
{% endif %}
|
||||
|
||||
## Voraussetzungen
|
||||
|
||||
Du solltest mit YAML und der Syntax für {% data variables.product.prodname_actions %} vertraut sein. Weitere Informationen finden Sie unter
|
||||
- [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)
|
||||
- [Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
|
||||
|
||||
Du solltest ein grundlegendes Verständnis von Java und dem Framework Ant haben. Weitere Informationen findest du im [Handbuch zu Apache Ant](https://ant.apache.org/manual/).
|
||||
|
||||
{% data reusables.actions.enterprise-setup-prereq %}
|
||||
|
||||
## Verwenden des Ant-Starterworkflows
|
||||
|
||||
{% data variables.product.prodname_dotcom %} bietet einen Ant-Starterworkflow, der für die meisten Ant-basierten Java-Projekte funktionieren wird. Weitere Informationen findest du im [Ant-Starterworkflow](https://github.com/actions/starter-workflows/blob/main/ci/ant.yml).
|
||||
|
||||
Um schnell loszulegen, kannst du beim Erstellen eines neuen Workflows den vorkonfigurierten Ant-Starterworkflow auswählen. Weitere Informationen findest du in der [Schnellstartanleitung für {% data variables.product.prodname_actions %}](/actions/quickstart).
|
||||
|
||||
Du kannst diesen Workflow auch manuell hinzufügen, indem du eine neue Datei im Verzeichnis `.github/workflows` deines Repositorys erstellst.
|
||||
|
||||
```yaml{:copy}
|
||||
name: Java CI
|
||||
|
||||
on: [push]
|
||||
|
||||
jobs:
|
||||
build:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Set up JDK 11
|
||||
uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
- name: Build with Ant
|
||||
run: ant -noinput -buildfile build.xml
|
||||
```
|
||||
|
||||
Dieser Workflow führt die folgenden Schritte aus:
|
||||
|
||||
1. Im Schritt `checkout` wird eine Kopie deines Repositorys auf den Runner heruntergeladen.
|
||||
2. Im Schritt `setup-java` wird das Java 11-JDK von Adoptium konfiguriert.
|
||||
3. Der Schritt „Mit Ant erstellen“ führt das Standardziel in deiner Datei `build.xml` im nicht-interaktiven Modus aus.
|
||||
|
||||
Die Standardstarterworkflows sind ausgezeichnete Ausgangspunkte beim Erstellen von Build- und Testworkflows, und du kannst den Starterworkflow den Anforderungen deines Projekts anpassen.
|
||||
|
||||
{% data reusables.actions.example-github-runner %}
|
||||
|
||||
{% data reusables.actions.java-jvm-architecture %}
|
||||
|
||||
## Deinen Code bauen und testen
|
||||
|
||||
Du kannst die gleichen Befehle verwenden, die Du auch lokal verwendest, um Deinen Code zu bauen und zu testen.
|
||||
|
||||
Der Starterworkflow führt das in der Datei _build.xml_ angegebene Standardziel aus. Dein Standard-Ziel wird normalerweise eingestellt, um Klassen zu bauen, Tests durchzuführen und Klassen in ihr verteilbares Format (z.B . eine JAR-Datei) zu paketieren.
|
||||
|
||||
Wenn Du zum Bauen Deines Projekts andere Befehle verwenden oder ein anderes Ziel auszuführen möchtest, kannst Du dies angeben. Du kannst beispielsweise das `jar`-Ziel ausführen, das in deiner Datei `_build-ci.xml_` konfiguriert ist.
|
||||
|
||||
```yaml{:copy}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
- name: Run the Ant jar target
|
||||
run: ant -noinput -buildfile build-ci.xml jar
|
||||
```
|
||||
|
||||
## Workflow-Daten als Artefakte paketieren
|
||||
|
||||
Nachdem sowohl Build erfolgreich war und deine Tests bestanden hat, wirst du die resultierenden Java-Pakete als Build-Artefakt hochladen wollen. Dies speichert die gebauten Pakete als Teil der Workflow-Ausführung und ermöglicht Dir, sie herunterzuladen. Artefakte können Dir helfen, Pull-Requests in deiner lokalen Umgebung zu testen und zu debuggen, bevor sie zusammengeführt werden („merge“). Weitere Informationen findest du unter [Speichern von Workflowdaten mithilfe von Artefakten](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts).
|
||||
|
||||
Ant erstellt normalerweise Ausgabedateien wie JAR-, EAR- oder WAR-Dateien im Verzeichnis `build/jar`. Du kannst den Inhalt dieses Verzeichnisses mit der Aktion `upload-artifact` hochladen.
|
||||
|
||||
```yaml{:copy}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
|
||||
- run: ant -noinput -buildfile build.xml
|
||||
- uses: {% data reusables.actions.action-upload-artifact %}
|
||||
with:
|
||||
name: Package
|
||||
path: build/jar
|
||||
```
|
||||
@@ -0,0 +1,149 @@
|
||||
---
|
||||
title: Java bauen und testen mit Gradle
|
||||
intro: 'Du kannst einen Workflow für Continuous Integration (CI) in GitHub Actions erstellen, um dein Java-Projekt mit Gradle zu kompilieren und zu testen.'
|
||||
redirect_from:
|
||||
- /actions/language-and-framework-guides/building-and-testing-java-with-gradle
|
||||
- /actions/guides/building-and-testing-java-with-gradle
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: tutorial
|
||||
topics:
|
||||
- CI
|
||||
- Java
|
||||
- Gradle
|
||||
shortTitle: Build & test Java & Gradle
|
||||
ms.openlocfilehash: 00fa6888a45dda090df51260795717bc994be022
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '147410443'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## Einführung
|
||||
|
||||
Dieser Leitfaden zeigt Dir, wie du einen Workflow erstellen kannst, der eine kontinuierliche Integration (CI) für dein Java-Projekt mit Hilfe des Build-Systems Gradle durchführt. Der Workflow, den du erstellst, zeigt Dir, wenn Commits zu einem Pull-Request zu Build- oder Testfehlern für deinen Standard-Zweig führen. Dieser Ansatz kann dazu beitragen, dass dein Code immer brauchbar ist. Du kannst deinen CI-Workflow so erweitern, dass er {% ifversion actions-caching %}Dateien zwischenspeichert und{% endif %} Artefakte aus einer Workflowausführung hochlädt.
|
||||
|
||||
{% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} {% else %} {% data variables.product.prodname_dotcom %}-gehostete Runner verfügen über einen Toolcache mit vorinstallierter Software, die Java Development Kits (JDKs) und Gradle umfasst. Eine Liste der Software und der vorinstallierten Versionen für JDK und Gradle findest du unter „[Spezifikationen für {% data variables.product.prodname_dotcom %}-gehostete Runner](/actions/reference/specifications-for-github-hosted-runners/#supported-software)“.
|
||||
{% endif %}
|
||||
|
||||
## Voraussetzungen
|
||||
|
||||
Du solltest mit YAML und der Syntax für {% data variables.product.prodname_actions %} vertraut sein. Weitere Informationen finden Sie unter
|
||||
- [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)
|
||||
- [Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
|
||||
|
||||
Du solltest ein grundlegendes Verständnis von Java und dem Framework Gradle haben. Weitere Informationen findest du in der Gradle-Dokumentation unter [Erste Schritte](https://docs.gradle.org/current/userguide/getting_started.html).
|
||||
|
||||
{% data reusables.actions.enterprise-setup-prereq %}
|
||||
|
||||
## Verwenden des Gradle-Starterworkflows
|
||||
|
||||
{% data variables.product.prodname_dotcom %} bietet einen Gradle-Starterworkflow, der für die meisten Gradle-basierten Java-Projekte funktioniert. Weitere Informationen findest du unter [Gradle-Starterworkflow](https://github.com/actions/starter-workflows/blob/main/ci/gradle.yml).
|
||||
|
||||
Um schnell loszulegen, kannst du beim Erstellen eines neuen Workflows den vorkonfigurierten Gradle-Starterworkflow auswählen. Weitere Informationen findest du in der [Schnellstartanleitung für {% data variables.product.prodname_actions %}](/actions/quickstart).
|
||||
|
||||
Du kannst diesen Workflow auch manuell hinzufügen, indem du eine neue Datei im Verzeichnis `.github/workflows` deines Repositorys erstellst.
|
||||
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Java CI
|
||||
|
||||
on: [push]
|
||||
|
||||
jobs:
|
||||
build:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Set up JDK 11
|
||||
uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
- name: Validate Gradle wrapper
|
||||
uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
|
||||
- name: Build with Gradle
|
||||
uses: gradle/gradle-build-action@67421db6bd0bf253fb4bd25b31ebb98943c375e1
|
||||
with:
|
||||
arguments: build
|
||||
```
|
||||
|
||||
Dieser Workflow führt die folgenden Schritte aus:
|
||||
|
||||
1. Im Schritt `checkout` wird eine Kopie deines Repositorys auf den Runner heruntergeladen.
|
||||
2. Im Schritt `setup-java` wird das Java 11-JDK von Adoptium konfiguriert.
|
||||
3. Im Schritt „Valid Gradle wrapper“ werden die Prüfsummen von Gradle Wrapper JAR-Dateien überprüft, die in der Quellstruktur vorhanden sind.
|
||||
4. Im Schritt „Build with Gradle“ wird mit der Aktion `gradle/gradle-build-action`, die von der Gradle-Organisation auf {% data variables.product.prodname_dotcom %} bereitgestellt wird, ein Build ausgeführt. Die Aktion umfasst das Aufrufen von Gradle, das Sammeln von Ergebnissen und das Zwischenspeichern des Status zwischen Aufträgen. Weitere Informationen findest du unter [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action).
|
||||
|
||||
Die Standardstarterworkflows sind ausgezeichnete Ausgangspunkte beim Erstellen von Build- und Testworkflows, und du kannst den Starterworkflow den Anforderungen deines Projekts anpassen.
|
||||
|
||||
{% data reusables.actions.example-github-runner %}
|
||||
|
||||
{% data reusables.actions.java-jvm-architecture %}
|
||||
|
||||
## Deinen Code bauen und testen
|
||||
|
||||
Du kannst die gleichen Befehle verwenden, die du auch lokal verwendest, um deinen Code zu bauen und zu testen.
|
||||
|
||||
Der Starterworkflow führt standardmäßig die `build`-Aufgabe aus. In der Standard-Gradle-Konfiguration lädt dieser Befehl Abhängigkeiten herunter, baut Klassen, führt Tests durch und paketiert Klassen in ihr verteilbares Format, zum Beispiel eine JAR-Datei.
|
||||
|
||||
Wenn du zum Bauen deines Projekts andere Befehle verwenden oder einen anderen Task auszuführen möchtest, kannst du dies angeben. Du kannst beispielsweise die `package`-Aufgabe ausführen, die in der _ci.gradle_-Datei konfiguriert ist.
|
||||
|
||||
```yaml{:copy}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
- name: Validate Gradle wrapper
|
||||
uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
|
||||
- name: Run the Gradle package task
|
||||
uses: gradle/gradle-build-action@67421db6bd0bf253fb4bd25b31ebb98943c375e1
|
||||
with:
|
||||
arguments: -b ci.gradle package
|
||||
```
|
||||
|
||||
{% ifversion actions-caching %}
|
||||
|
||||
## Abhängigkeiten „cachen“ (zwischenspeichern)
|
||||
|
||||
Deine Buildabhängigkeiten können zwischengespeichert werden, um deine Workflowausführungen zu beschleunigen. Nach einer erfolgreichen Ausführung werden wichtige Teile des Basisverzeichnisses für Gradle-Benutzer von `gradle/gradle-build-action` zwischengespeichert. In künftigen Aufträgen wird der Cache wiederhergestellt, sodass Buildskripts nicht neu kompiliert werden müssen und Abhängigkeiten nicht erneut aus Remotepaketrepositorys heruntergeladen werden müssen.
|
||||
|
||||
Das Zwischenspeichern ist standardmäßig aktiviert, wenn die Aktion `gradle/gradle-build-action` verwendet wird. Weitere Informationen findest du unter [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action#caching).
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Workflow-Daten als Artefakte paketieren
|
||||
|
||||
Nachdem sowohl Build erfolgreich war und deine Tests bestanden hat, wirst du die resultierenden Java-Pakete als Build-Artefakt hochladen wollen. Dies speichert die gebauten Pakete als Teil der Workflow-Ausführung und ermöglicht Dir, sie herunterzuladen. Artefakte können Dir helfen, Pull-Requests in deiner lokalen Umgebung zu testen und zu debuggen, bevor sie zusammengeführt werden („merge“). Weitere Informationen findest du unter [Speichern von Workflowdaten mithilfe von Artefakten](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts).
|
||||
|
||||
Gradle erstellt normalerweise Ausgabedateien wie JARs, EARs oder WARs im Verzeichnis `build/libs`. Du kannst den Inhalt dieses Verzeichnisses mit der Aktion `upload-artifact` hochladen.
|
||||
|
||||
```yaml{:copy}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
- name: Validate Gradle wrapper
|
||||
uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
|
||||
- name: Build with Gradle
|
||||
uses: gradle/gradle-build-action@67421db6bd0bf253fb4bd25b31ebb98943c375e1
|
||||
with:
|
||||
arguments: build
|
||||
- uses: {% data reusables.actions.action-upload-artifact %}
|
||||
with:
|
||||
name: Package
|
||||
path: build/libs
|
||||
```
|
||||
@@ -0,0 +1,145 @@
|
||||
---
|
||||
title: Java bauen und testen mit Maven
|
||||
intro: 'Du kannst einen Workflow für Continuous Integration (CI) in GitHub Actions erstellen, um dein Java-Projekt mit Maven zu erstellen und zu testen.'
|
||||
redirect_from:
|
||||
- /actions/language-and-framework-guides/building-and-testing-java-with-maven
|
||||
- /actions/guides/building-and-testing-java-with-maven
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: tutorial
|
||||
topics:
|
||||
- CI
|
||||
- Java
|
||||
- Maven
|
||||
shortTitle: Build & test Java with Maven
|
||||
ms.openlocfilehash: 59d8961a7fdd1d8b84a05b8762bb09be3d2ab01c
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: de-DE
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146179807'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## Einführung
|
||||
|
||||
Dieser Leitfaden zeigt Dir, wie du einen Workflow erstellen kannst, der eine kontinuierliche Integration (CI) für dein Java-Projekt mit Hilfe des Software-Projektmanagement-Tools Maven durchführt. Der Workflow, den du erstellst, zeigt Dir, wenn Commits zu einem Pull-Request zu Build- oder Testfehlern für deinen Standard-Zweig führen. Dieser Ansatz kann dazu beitragen, dass dein Code immer brauchbar ist. Du kannst deinen CI-Workflow so erweitern, dass er {% ifversion actions-caching %}Dateien zwischenspeichert und{% endif %} Artefakte aus einer Workflowausführung hochlädt.
|
||||
|
||||
Von {% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} {% else %} {% data variables.product.prodname_dotcom %} gehostete Runner verfügen über einen Toolcache mit vorinstallierter Software, die Java Development Kits (JDKs) und Maven umfasst. Eine Liste der Software und der vorinstallierten Versionen für JDK und Maven findest du unter [Spezifikationen für von {% data variables.product.prodname_dotcom %} gehostete Runner](/actions/reference/specifications-for-github-hosted-runners/#supported-software).
|
||||
{% endif %}
|
||||
|
||||
## Voraussetzungen
|
||||
|
||||
Du solltest mit YAML und der Syntax für {% data variables.product.prodname_actions %} vertraut sein. Weitere Informationen finden Sie unter
|
||||
- [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)
|
||||
- [Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
|
||||
|
||||
Du solltest ein grundlegendes Verständnis von Java und dem Framework Maven haben. Weitere Informationen findest du in der Maven-Dokumentation im [Maven-Leitfaden zu den ersten Schritten](http://maven.apache.org/guides/getting-started/index.html).
|
||||
|
||||
{% data reusables.actions.enterprise-setup-prereq %}
|
||||
|
||||
## Verwenden des Maven-Startworkflows
|
||||
|
||||
{% data variables.product.prodname_dotcom %} bietet einen Maven-Startworkflow, der für die meisten Maven-basierten Java-Projekte funktioniert. Weitere Informationen findest du unter [Maven-Startworkflow](https://github.com/actions/starter-workflows/blob/main/ci/maven.yml).
|
||||
|
||||
Um schnell loszulegen, kannst du beim Erstellen eines neuen Workflows den vorkonfigurierten Maven-Startworkflow auswählen. Weitere Informationen findest du in der [Schnellstartanleitung für {% data variables.product.prodname_actions %}](/actions/quickstart).
|
||||
|
||||
Du kannst diesen Workflow auch manuell hinzufügen, indem du eine neue Datei im Verzeichnis `.github/workflows` deines Repositorys erstellst.
|
||||
|
||||
```yaml{:copy}
|
||||
name: Java CI
|
||||
|
||||
on: [push]
|
||||
|
||||
jobs:
|
||||
build:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Set up JDK 11
|
||||
uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
- name: Build with Maven
|
||||
run: mvn --batch-mode --update-snapshots package
|
||||
```
|
||||
|
||||
Dieser Workflow führt die folgenden Schritte aus:
|
||||
|
||||
1. Im Schritt `checkout` wird eine Kopie deines Repositorys auf den Runner heruntergeladen.
|
||||
2. Im Schritt `setup-java` wird das Java 11-JDK von Adoptium konfiguriert.
|
||||
3. Der Schritt „Mit Maven erstellen“ führt das Maven-`package`-Ziel im nicht interaktiven Modus aus, um sicherzustellen, dass dein Code erstellt wird, Tests erfolgreich durchgeführt werden und ein Paket erstellt werden kann.
|
||||
|
||||
Die Standardstartworkflows sind ausgezeichnete Ausgangspunkte beim Erstellen von Build- und Testworkflows, und du kannst den Startworkflow den Anforderungen deines Projekts anpassen.
|
||||
|
||||
{% data reusables.actions.example-github-runner %}
|
||||
|
||||
{% data reusables.actions.java-jvm-architecture %}
|
||||
|
||||
## Deinen Code bauen und testen
|
||||
|
||||
Du kannst die gleichen Befehle verwenden, die du auch lokal verwendest, um deinen Code zu bauen und zu testen.
|
||||
|
||||
Der Startworkflow führt standardmäßig das `package`-Ziel aus. In der Standard-Maven-Konfiguration lädt dieser Befehl Abhängigkeiten herunter, baut Klassen, führt Tests durch und paketiert Klassen in ihr verteilbares Format, zum Beispiel eine JAR-Datei.
|
||||
|
||||
Wenn du zum Bauen deines Projekts andere Befehle verwenden oder ein anderes Ziel auszuführen möchtest, kannst du dies angeben. Du kannst beispielsweise das `verify`-Ziel ausführen, das in einer Datei _pom-ci.xml_ konfiguriert ist.
|
||||
|
||||
```yaml{:copy}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
- name: Run the Maven verify phase
|
||||
run: mvn --batch-mode --update-snapshots verify
|
||||
```
|
||||
|
||||
{% ifversion actions-caching %}
|
||||
|
||||
## Abhängigkeiten „cachen“ (zwischenspeichern)
|
||||
|
||||
Du kannst deine Abhängigkeiten zwischenspeichern, um die Workflow-Ausführungen zu beschleunigen. Nach einer erfolgreichen Ausführung wird dein lokales Maven-Repository in einem Cache gespeichert. Bei zukünftigen Workflow-Ausführungen wird der Cache wiederhergestellt, so dass Abhängigkeiten nicht aus entfernten Maven-Repositories heruntergeladen werden müssen. Du kannst Abhängigkeiten einfach mithilfe der [`setup-java`-Aktion](https://github.com/marketplace/actions/setup-java-jdk) zwischenspeichern oder die [`cache`-Aktion](https://github.com/actions/cache) für eine benutzerdefinierte und erweiterte Konfiguration verwenden.
|
||||
|
||||
```yaml{:copy}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- name: Set up JDK 11
|
||||
uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
cache: maven
|
||||
- name: Build with Maven
|
||||
run: mvn --batch-mode --update-snapshots verify
|
||||
```
|
||||
|
||||
Dieser Workflow speichert den Inhalt deines lokalen Maven-Repositorys, das sich im Verzeichnis `.m2` des Basisverzeichnisses auf dem Runner befindet. Der Cacheschlüssel ist der Hashinhalt von _pom.xml_, sodass Änderungen an _pom.xml_ den Cache ungültig machen.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Workflow-Daten als Artefakte paketieren
|
||||
|
||||
Nachdem sowohl Build erfolgreich war und deine Tests bestanden hat, wirst du die resultierenden Java-Pakete als Build-Artefakt hochladen wollen. Dies speichert die gebauten Pakete als Teil der Workflow-Ausführung und ermöglicht Dir, sie herunterzuladen. Artefakte können Dir helfen, Pull-Requests in deiner lokalen Umgebung zu testen und zu debuggen, bevor sie zusammengeführt werden („merge“). Weitere Informationen findest du unter [Speichern von Workflowdaten mithilfe von Artefakten](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts).
|
||||
|
||||
Maven erstellt normalerweise Ausgabedateien wie JARs, EARs oder WARs im Verzeichnis `target`. Um diese als Artefakte hochzuladen, kannst du sie in ein neues Verzeichnis kopieren, welches Artefakte zum Hochladen enthält. Zum Beispiel kannst du ein Verzeichnis namens `staging` erstellen. Anschließend kannst du den Inhalt dieses Verzeichnisses mithilfe der Aktion `upload-artifact` hochladen.
|
||||
|
||||
```yaml{:copy}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-checkout %}
|
||||
- uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
- run: mvn --batch-mode --update-snapshots verify
|
||||
- run: mkdir staging && cp target/*.jar staging
|
||||
- uses: {% data reusables.actions.action-upload-artifact %}
|
||||
with:
|
||||
name: Package
|
||||
path: staging
|
||||
```
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user