@@ -63,7 +63,7 @@
 
   // Lifecycle commands
   // Start a web server and keep it running
-  "postStartCommand": "nohup bash -c 'npm start &'",
+  "postStartCommand": "nohup bash -c 'npm ci && npm start &'",
   // Set port 4000 to be public
   "postAttachCommand": "gh cs ports visibility 4000:public -c \"$CODESPACE_NAME\"",
 
 
@@ -8,7 +8,7 @@
 # ---------------------------------------------------------------
 # To update the sha:
 # https://github.com/github/gh-base-image/pkgs/container/gh-base-image%2Fgh-base-noble
-FROM ghcr.io/github/gh-base-image/gh-base-noble:20251217-105955-g05726ec4c AS base
+FROM ghcr.io/github/gh-base-image/gh-base-noble:20260113-125234-g605df3bee AS base
 
 # Install curl for Node install and determining the early access branch
 # Install git for cloning docs-early-access & translations repos
 
@@ -13,19 +13,26 @@ redirect_from:
   - /account-and-profile/concepts/personal-account-management
 ---
 
+{% ifversion ghes < 3.21 %}
 ## About converting your personal account
 
 Converting a personal account into an organization allows you move to a shared account where a large number of people can collaborate across many projects at once. 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 %}](/billing/managing-the-plan-for-your-github-account/about-billing-for-plans) without the need to re-enter payment information, adjust your billing cycle, or double pay at any time
-{%- endif %}
 
 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 [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators).
 
 To convert your personal account into an organization, see [AUTOTITLE](/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization).
 
+{% else %}
+
+## About moving your work to an organization
+
+You can move repositories and projects from your personal account to an organization while keeping your personal account intact. This enables team collaboration with granular permissions across your existing work.
+
+For more information, see [AUTOTITLE](/account-and-profile/how-tos/account-management/moving-your-work-to-an-organization).
+{% endif %}
+
 ## 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 %}
 
@@ -12,9 +12,7 @@ redirect_from:
   - /account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/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: '*'
-  ghec: '*'
+  ghes: '<3.21'
 topics:
   - Accounts
 shortTitle: Convert your account
@@ -25,9 +23,7 @@ contentType: how-tos
 
 The personal account you want to convert cannot be a member of any organizations. If the personal account you want to convert is a member of an organization, you must leave the organization before you can convert the account.
 
-{% ifversion ghes %}
-You may not be able to convert a personal account into an organization, if an enterprise owner has set a policy at the enterprise level. See, [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations).
-{% endif %}
+You may not be able to convert a personal account into an organization if an enterprise owner has set a policy at the enterprise level. See, [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations).
 
 ## Keep your personal account and create a new organization manually
 
@@ -56,7 +52,4 @@ To convert your personal account into an organization, follow these steps:
 
 * [AUTOTITLE](/account-and-profile/reference/personal-account-reference#side-effects-of-converting-an-account-to-an-organization)
 * [AUTOTITLE](/organizations/organizing-members-into-teams)
-{% ifversion fpt or ghec %}
-* [AUTOTITLE](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)
-{% endif %}
 * [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization)
@@ -1,6 +1,6 @@
 ---
 title: Managing your personal account
-intro: You can manage your personal account on {% data variables.product.github %}. For example, you can {% ifversion fpt or ghec %}manage multiple accounts, {% endif %}convert an account to an organization, or delete an account.
+intro: You can manage your personal account on {% data variables.product.github %}. For example, you can change your username, {% ifversion fpt or ghec %}manage multiple accounts, {% endif %}{% ifversion ghes < 3.21 %}convert an account to an organization, {% else %}move your work to an organization, {% endif %}or delete an account.
 shortTitle: Personal account management
 versions:
   fpt: '*'
@@ -12,6 +12,7 @@ children:
   - /managing-multiple-accounts
   - /merging-multiple-personal-accounts
   - /changing-your-username
+  - /moving-your-work-to-an-organization
   - /converting-a-user-into-an-organization
   - /unlinking-your-email-address-from-a-locked-account
   - /deleting-your-personal-account
 
@@ -0,0 +1,32 @@
+---
+title: Moving your work to an organization
+intro: You can transfer repositories and projects from your personal account to a new or existing organization through your account settings.
+versions:
+  fpt: '*'
+  ghes: '>= 3.21'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Move work to organization
+---
+
+## Keeping your username for the organization
+
+If you want your new organization to use your current personal account username, you'll need to rename your personal account first:
+
+1. Change your personal account username to something new. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username).
+1. Create an organization using your original username, then follow the steps below to move your work.
+
+## Moving your work to an organization
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.organizations %}
+1. Under the "Move to an organization" section, click **Move work to an organization**.
+1. Follow the prompts to transfer any of your repositories and projects to a new or existing organization. {% ifversion fpt or ghec %}For more information about the plans available for your team, see [AUTOTITLE](/get-started/learning-about-github/githubs-plans).{% endif %}
+1. Once done assigning your work to its new location, click **Move to an organization**, then click **Go to your organization**.
+
+## Further reading
+
+- [AUTOTITLE](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)
+- [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)
@@ -57,6 +57,9 @@ To configure a workflow for image generation:
   * Each job that includes the `snapshot` keyword creates a separate image. To generate only one image or image version, include all workflow steps in a single job.
   * Each successful run of a job that includes the `snapshot` keyword creates a new version of that image.
 
+ > [!NOTE]
+ > {% data variables.product.company_short %} recommends configuring image generation as a scheduled workflow on a weekly basis. This approach ensures dependencies remain up-to-date and have the latest security patches. For more information, see [AUTOTITLE](/actions/using-workflows/events-that-trigger-workflows#schedule).
+
 It can take some time for your image to be fully generated and ready to use after the workflow completes. Provisioning time varies based on runner size and configuration, and may take several hours for larger runners.
 
 The image is generated only when the job completes successfully. This prevents new image versions from being created when a workflow fails or ends in an incomplete state.
 
@@ -11,6 +11,7 @@ children:
   - /view-job-execution-time
   - /add-a-status-badge
   - /use-workflow-run-logs
+  - /view-job-condition-logs
   - /enable-debug-logging
 redirect_from:
   - /actions/monitoring-and-troubleshooting-workflows/monitoring-workflows
 
@@ -0,0 +1,40 @@
+---
+title: Viewing job condition expression logs
+shortTitle: View job condition logs
+intro: 'Learn how to access and interpret expression evaluation logs for job-level `if` conditions in {% data variables.product.prodname_actions %}.'
+versions:
+  fpt: '*'
+  ghec: '*'
+contentType: how-tos
+---
+
+When a job's `if` condition is evaluated, {% data variables.product.prodname_actions %} logs the expression evaluation to help you understand the result. This is useful for debugging both why a job was skipped and why a job ran when you expected it to be skipped.
+
+## Accessing expression logs
+
+1. Navigate to the workflow run summary.
+1. Click on the job.
+1. Click **{% octicon "gear" aria-label="The Gear icon" %}**.
+1. Select **Download log archive**.
+1. Extract the ZIP file and open the `JOB-NAME/system.txt` file.
+
+## Understanding the log output
+
+The system log shows the expression evaluation:
+
+```text
+Evaluating: (success() && ((github.repository == 'octo-org/octo-repo-prod')))
+Expanded: (true && (('my-username/octo-repo-prod' == 'octo-org/octo-repo-prod')))
+Result: false
+```
+
+| Line | Description |
+|------|-------------|
+| **Evaluating** | The original `if` expression from your workflow file. |
+| **Expanded** | The expression with context values substituted. This shows you exactly what values were used at runtime. |
+| **Result** | The final evaluation result (`true` or `false`). |
+
+In this example, the expanded line reveals that `github.repository` was `'my-username/octo-repo-prod'` (not `'octo-org/octo-repo-prod'`), which caused the condition to evaluate to `false`.
+
+> [!NOTE]
+> Expression logs are only available for job-level `if` conditions. For step-level conditions, you can enable debug logging to see expression evaluation in the job logs. For more information, see [AUTOTITLE](/actions/how-tos/monitor-workflows/enable-debug-logging).