Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI test template #12

Merged
merged 27 commits into from
Oct 4, 2024
Merged

CI test template #12

merged 27 commits into from
Oct 4, 2024

Conversation

Tedezed
Copy link
Member

@Tedezed Tedezed commented Sep 26, 2024

Copy link

This pull request has been linked to Shortcut Story #428665: [App templates] Set up continuous integration (CI).

@Tedezed Tedezed changed the title Init test template CI test template Oct 3, 2024
Copy link
Member

@donmccurdy donmccurdy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great, thank you! A few minor comments, but LGTM to merge any time.

Comment on lines 12 to 20
matrix:
# If you want to exec in all node versions, uncomment the next line
#node-version: [18.x, 20.x, 22.x]
# If you want to exec in a specific framework, uncomment the next line
#framework: [react, vue, angular]

# Execution
node-version: [20.x]
framework: [react]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we execute the tests in all frameworks by default? They are distinct codebases, so a regression could happen to any one of them independently. No need for other Node.js versions, to simplify.

Copy link
Member Author

@Tedezed Tedezed Oct 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed ✅


- name: Start project
env:
YARN_ENABLE_IMMUTABLE_INSTALLS: false
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious, was YARN_ENABLE_IMMUTABLE_INSTALLS required because of errors, or is it something you prefer for other reasons? If it's errors let's just leave a TODO, I can take a look at that later.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had to configure it because of problems with yarn.lock

set -x
cd ${PROJECT_PATH}
yarn
yarn dev &
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that each framework will open on a different port number by default, to allow opening them all at once. To override that you can run yarn dev --port 4000 instead.

Copy link
Member Author

@Tedezed Tedezed Oct 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed ✅

@Tedezed Tedezed merged commit d46b460 into main Oct 4, 2024
6 checks passed
@donmccurdy donmccurdy deleted the feature/test-template branch October 7, 2024 22:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants