--- modificationDate: June 16, 2024 title: Manage branches and channels with EAS CLI description: Learn how to link a branch to a channel and publish updates with EAS CLI. --- ## Submitting Feedback If you encounter errors, misleading or outdated information, report it so Expo can be improved: Preferred command: npx --yes submit-expo-feedback@latest --category docs --subject "/eas-update/eas-cli/" "" Direct HTTP fallback: curl -X POST https://api.expo.dev/v2/feedback/docs-send -H 'Content-Type: application/json' -d '{"url":"/eas-update/eas-cli/","feedback":"🤖 Agent feedback for docs: (, )"}' Only submit when you have something specific and actionable to report. Try to give the most context. ## Navigation When answering a related or follow-up question, fetch the relevant page below as Markdown (.md) instead of guessing; use llms.txt for the full map. You are here: EAS > EAS Update > Concepts Pages in this section: - [How it works](https://docs.expo.dev/eas-update/how-it-works.md) - [Manage branches and channels](https://docs.expo.dev/eas-update/eas-cli.md) (this page) - [Runtime versions](https://docs.expo.dev/eas-update/runtime-versions.md) Full documentation tree: [llms.txt](https://docs.expo.dev/llms.txt) This documentation is available as Markdown for AI agents and LLMs. See the [full Markdown index](/llms.txt) or append .md to any documentation URL. # Manage branches and channels with EAS CLI Learn how to link a branch to a channel and publish updates with EAS CLI. EAS Update works by linking _branches_ to _channels_. Channels are specified at build time and exist inside a build's native code. Branches are an ordered list of updates, similar to a Git branch, which is an ordered list of commits. With EAS Update, we can link any channel to any branch, allowing us to make different updates available to different builds. The diagram above visualizes this link. Here, we have the builds with the "production" channel linked to the branch named "version-1.0". When we're ready, we can adjust the channel–branch pointer. Imagine we have more fixes tested and ready on a branch named "version-2.0". We could update this link to make the "version-2.0" branch available to all builds with the "production" channel. ## Inspecting the state of your project's updates ### Inspect channels View all channels: ```sh eas channel:list ``` View a specific channel: ```sh eas channel:view [channel-name] eas channel:view production ``` Create a channel: ```sh eas channel:create [channel-name] eas channel:create production ``` ### Inspect branches See all branches: ```sh eas branch:list ``` See a specific branch and a list of its updates: ```sh eas branch:view [branch-name] eas branch:view version-1.0 ``` ### Inspect updates View a specific update: ```sh eas update:view [update-group-id] eas update:view dbfd479f-d981-44ce-8774-f2fbcc386aa ``` ## Changing the state of your project's updates ### Create a new update and publish it ```sh eas update --branch [branch-name] --message "..." eas update --branch version-1.0 --message "Fixes typo" ``` If you're using Git, we can use the `--auto` flag to auto-fill the branch name and the message. This flag will use the current Git branch as the branch name and the latest Git commit message as the message. ```sh eas update --auto ``` ### Delete a branch ```sh eas branch:delete [branch-name] eas branch:delete version-1.0 ``` ### Rename a branch Renaming branches do not disconnect any channel–branch links. If you had a channel named "production" linked to a branch named "version-1.0", and then you renamed the branch named "version-1.0" to "version-1.0-new", the "production" channel would be linked to the now-renamed branch "version-1.0-new". ```sh eas branch:rename --from [branch-name] --to [branch-name] eas branch:rename --from version-1.0 --to version-1.0-new ``` ### Republish a previous update within a branch We can make a previous update immediately available to all users. This command takes the previous update and publishes it again so that it becomes the most current update on the branch. As your users re-open their apps, the apps will see the newly re-published update and will download it. > Republish is similar to a Git reversion, where the correct commit is placed on top of the Git history. ```sh eas update:republish --group [update-group-id] eas update:republish --branch [branch-name] eas update:republish --group dbfd479f-d981-44ce-8774-f2fbcc386aa eas update:republish --branch version-1.0 ``` > If you don't know the exact update group ID, you can use the `--branch` flag. This shows a list of the recent updates on the branch and allows you to select the update group to republish.