From 54e07b3866d35f1639c47f1a9625fbf87d429101 Mon Sep 17 00:00:00 2001 From: Olayinka Atobiloye Date: Fri, 10 Feb 2023 16:44:05 +0000 Subject: [PATCH 1/5] Added a section for the effect of username changes on codeowners file --- .../changing-your-github-username.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md index 3638e5d3cbe2..54ac7f4a16e6 100644 --- a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md @@ -85,6 +85,11 @@ After changing your username, links to your previous profile page, such as `http 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. +## CODEOWNERS files + +After changing your username, CODEOWNERS files will need to be manually updated. When viewing the CODEOWNERS files from the web, a warning will show if the file contains any unknown user(s) or user(s) without write access. We recommend updating all relevant CODEOWNERS files with your new username. + + ## Changing your username {% data reusables.user-settings.access_settings %} From 94606b0cc85a6ed7c77673284f2c1812b1b4c2cf Mon Sep 17 00:00:00 2001 From: Olayinka Atobiloye Date: Fri, 10 Feb 2023 17:15:05 +0000 Subject: [PATCH 2/5] Fixed lintin g error. --- .../changing-your-github-username.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md index 54ac7f4a16e6..7fdff406a651 100644 --- a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md @@ -89,7 +89,6 @@ After changing your username, the URLs to any public or secret gists will also c After changing your username, CODEOWNERS files will need to be manually updated. When viewing the CODEOWNERS files from the web, a warning will show if the file contains any unknown user(s) or user(s) without write access. We recommend updating all relevant CODEOWNERS files with your new username. - ## Changing your username {% data reusables.user-settings.access_settings %} From 1a4eca4cdc8c9839e7c60f0c289dc497a0d1d1eb Mon Sep 17 00:00:00 2001 From: Olayinka Atobiloye Date: Sun, 12 Feb 2023 00:42:06 +0000 Subject: [PATCH 3/5] Added a note for using contexts in workflows. --- .../using-jobs/using-conditions-to-control-job-execution.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/actions/using-jobs/using-conditions-to-control-job-execution.md b/content/actions/using-jobs/using-conditions-to-control-job-execution.md index 0bd46fa968be..cf61ad1395d5 100644 --- a/content/actions/using-jobs/using-conditions-to-control-job-execution.md +++ b/content/actions/using-jobs/using-conditions-to-control-job-execution.md @@ -26,3 +26,9 @@ miniTocMaxHeadingLevel: 4 You would see the following status on a skipped job: ![Skipped-required-run-details](/assets/images/help/repository/skipped-required-run-details.png) + +{% note %} + +**Note:** In some parts of the workflow, you cannot use environment variables; but instead, you can use contexts to access the value of an environment variable. For more information, see ["Using the env context to access environment variable values"](https://docs.github.com/en/actions/learn-github-actions/variables#using-the-env-context-to-access-environment-variable-values). + +{% endnote %} From b427d2a3a706e18f761a4cfdb0163a1158f7270c Mon Sep 17 00:00:00 2001 From: hubwriter Date: Tue, 14 Feb 2023 08:16:17 +0000 Subject: [PATCH 4/5] Update content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md --- .../changing-your-github-username.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md index 7fdff406a651..144ad2f415e2 100644 --- a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md @@ -87,7 +87,7 @@ After changing your username, the URLs to any public or secret gists will also c ## CODEOWNERS files -After changing your username, CODEOWNERS files will need to be manually updated. When viewing the CODEOWNERS files from the web, a warning will show if the file contains any unknown user(s) or user(s) without write access. We recommend updating all relevant CODEOWNERS files with your new username. +After changing your username, CODEOWNERS files that include your old username will need to be manually updated. When you view the CODEOWNERS files on {% data variables.product.prodname_dotcom_the_website %}, an error message is displayed if the file contains any unknown users, or users without write access. We recommend updating all relevant CODEOWNERS files with your new username. For more information, see "[About code owners](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)." ## Changing your username From 480a3ca479c5383d17b0a14cac7288d26e462caa Mon Sep 17 00:00:00 2001 From: hubwriter Date: Tue, 14 Feb 2023 08:16:25 +0000 Subject: [PATCH 5/5] Update content/actions/using-jobs/using-conditions-to-control-job-execution.md --- .../using-jobs/using-conditions-to-control-job-execution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/using-jobs/using-conditions-to-control-job-execution.md b/content/actions/using-jobs/using-conditions-to-control-job-execution.md index cf61ad1395d5..091a2e0712e2 100644 --- a/content/actions/using-jobs/using-conditions-to-control-job-execution.md +++ b/content/actions/using-jobs/using-conditions-to-control-job-execution.md @@ -29,6 +29,6 @@ You would see the following status on a skipped job: {% note %} -**Note:** In some parts of the workflow, you cannot use environment variables; but instead, you can use contexts to access the value of an environment variable. For more information, see ["Using the env context to access environment variable values"](https://docs.github.com/en/actions/learn-github-actions/variables#using-the-env-context-to-access-environment-variable-values). +**Note:** In some parts of the workflow you cannot use environment variables. Instead you can use contexts to access the value of an environment variable. For more information, see "[Using the env context to access environment variable values](/actions/learn-github-actions/variables#using-the-env-context-to-access-environment-variable-values)." {% endnote %}