| /expo/packages/@expo/cli/src/utils/ |
| H A D | obj.ts | 3 const branches = key.split('.'); constant
6 while ((branch = branches.shift())) {
17 const branches = key.split('.'); constant
20 while ((branch = branches.shift())) {
21 if (branches.length === 0) {
|
| /expo/packages/expo-dev-launcher/bundle/queries/ |
| H A D | useBranchesForApp.tsx | 77 const branches: Branch[] = [];
98 branches.push(branch);
103 // side-effect: prime the cache with branches
111 branches,
118 branches: [],
131 ['branches', appId, queryOptions.pageSize],
177 const branches =
179 .flatMap((page) => page.branches)
182 …// incompatible branches are branches that have no compatible updates with the current runtimeVers…
192 data: branches,
[all …]
|
| H A D | useChannelsForApp.tsx | 26 branches: string[]; // branchNames
40 branches: updateChannel.updateBranches.map((branch) => branch.name),
|
| /expo/packages/expo-dev-launcher/bundle/screens/ |
| H A D | BranchesScreen.tsx | 25 data: branches,
39 if (branches.length > 0) {
57 {branches.length > 0 && hasNextPage && (
70 {branches.length === 0 && hasNextPage && (
105 <EmptyBranchesMessage branches={branches} incompatibleBranches={incompatibleBranches} />
115 const isLast = index === branches?.length - 1;
139 data={branches}
152 branches: Branch[];
157 if (branches.length === 0) {
167 Recently created branches
[all …]
|
| H A D | ExtensionsScreen.tsx | 41 data: branches,
134 branches={branches}
219 branches: Branch[];
227 branches,
240 if (branches.length === 0 && emptyBranches.length > 0) {
284 // no compatiable branches
285 if (branches.length === 0) {
294 <EmptyBranchesMessage branches={branches} incompatibleBranches={incompatibleBranches} />
299 // some compatible branches, possible some empty branches
307 {branches?.slice(0, 2).map((branch, index, arr) => {
[all …]
|
| /expo/packages/expo-dev-launcher/bundle/functions/ |
| H A D | getRecentRuntime.ts | 3 export function getRecentRuntime(branches: Branch[]) {
4 const recentBranchWithUpdates = branches.find((branch) => branch.updates.length > 0);
|
| /expo/packages/@expo/config-plugins/src/utils/ |
| H A D | obj.ts | 3 const branches = key.split('.'); constant
6 while ((branch = branches.shift())) {
|
| /expo/packages/@expo/config-plugins/build/utils/ |
| H A D | obj.js | 9 const branches = key.split('.'); constant
12 while (branch = branches.shift()) {
|
| H A D | obj.js.map | 1 …branches","split","current","branch","shift","undefined"],"sources":["../../src/utils/obj.ts"],"so…
|
| /expo/packages/expo-dev-launcher/bundle/components/ |
| H A D | EmptyBranchesMessage.tsx | 13 branches: Branch[];
18 branches = [],
25 // no compatible branches
26 if (branches.length === 0 && incompatibleBranches.length > 0) {
32 <Heading>There are no branches compatible with this development build.</Heading>
105 …return `However, there are ${numberOfCompatibleBranches} branches that are compatible with a diffe…
|
| /expo/.github/workflows/ |
| H A D | shell-app-android.yml | 2 # in order to be run on other branches using workflow_dispatch.
6 # to trigger the workflow on other (usually sdk-xx) branches
|
| H A D | shell-app-ios.yml | 2 # in order to be run on other branches using workflow_dispatch.
6 # to trigger the workflow on other (usually sdk-xx) branches
|
| H A D | test-suite-lint.yml | 6 branches: [main]
|
| H A D | expotools.yml | 6 branches: [main, 'sdk-*']
|
| H A D | expo-updates-cli.yml | 5 branches: [main]
|
| H A D | create-expo-app.yml | 5 branches: [main, 'sdk-*']
|
| H A D | home.yml | 11 branches: [main, 'sdk-*']
|
| H A D | native-component-list.yml | 13 branches: [main]
|
| /expo/packages/expo-dev-launcher/bundle/screens/__tests__/ |
| H A D | ExtensionsScreen.test.tsx | 144 test('eas updates see all branches press', async () => {
181 await waitFor(() => getByText(/see all branches/i));
183 fireEvent.press(getByText(/all branches/i));
190 test('eas updates no compatible branches state', async () => {
216 test('eas updates no branches state', async () => {
|
| H A D | BranchesScreen.test.tsx | 155 test('empty branches state', async () => {
176 test('no compatible branches state', async () => {
211 test.todo('recent empty branches are visible in the footer');
|
| /expo/guides/ |
| H A D | Git and Code Reviews.md | 5 - [Develop on feature branches](#develop-on-feature-branches)
22 …including the Expo platform repository. We generally develop on feature branches and then rebase t…
28 ## Develop on feature branches
30 We often work on new features on their own branches. This is the first step towards sending your co…
32 Name your branches something memorable for yourself. It’s common to accrue old branches and is help…
40 …n a per-branch basis. Tell it to use rebasing for your existing branches and all new branches with:
43 # Set rebase=true for your existing branches
47 # Set rebase=true for new branches in the future
55 Rebasing your feature branches often (`git rebase main`) also increases the likelihood your code wo…
61 …ounter after pulling and rebasing on top of your changes. Keep your feature branches close to main.
|
| /expo/docs/pages/eas-update/ |
| H A D | deployment-patterns.mdx | 25 - (b) We can create update branches that are environment-based, like "production" and "staging".
26 …- (c) We can create update branches that are version-based, like "version-1.0", which enables us t…
69 …We do not track release versions with branches. Instead, we'll have persistent "staging" and "prod…
75 **Publishing updates:** (b) Create update branches that are environment-based, like "staging" and "…
89 3. Set up `expo-github-action` to publish updates when merging commits to branches.
96 …e to your team, since deploying updates occurs when merging into GitHub branches named "staging" a…
111 **Publishing updates:** (b) Create update branches that are environment- and platform-based, like "…
125 …`expo-github-action` to publish updates to the required platforms when merging commits to branches.
162 3. Set up `expo-github-action` to publish updates when merging commits to branches.
184 …branches and EAS Update branches. It also creates a mapping between GitHub commits and EAS Update …
[all …]
|
| H A D | how-it-works.mdx | 44 We can think of EAS branches just like Git branches. Just as Git branches contain a list of commits…
60 To simplify this linking, by default we auto-link channels to branches of the same name. For instan…
67 …rks great if you have a deployment process where you have multiple consistent Git and EAS branches.
73 …have the ability to change the link between channels and branches. Imagine we name our branches li…
|
| H A D | eas-cli.mdx | 46 ### Inspect branches
48 See all branches:
100 Renaming branches do not disconnect any channel–branch links. If you had a channel named "productio…
|
| /expo/home/components/ |
| H A D | BranchListItem.tsx | 25 …* This component is used to render a list item for the branches section on the project screen and …
26 * the branches list page for an app.
|