Skip to content

Conversation

enrico-kaack-comp
Copy link
Contributor

What this PR does / why we need it:
This Pr introduces a simple build step in the pipeline on PR opened/synchronize.

Will be later expanded with tests, linting etc.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

node-version: 22

- name: Install dependencies
run: npm i
Copy link
Contributor

@andreaskienle andreaskienle Mar 18, 2025

Choose a reason for hiding this comment

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

In a pipeline I think npm ci would be better. But our lockfile should then be reliable. And I’m not sure about that, as there are bun.lock, package-lock.json and yarn.lock 🤯

Could also leave it like this for now (npm i in the pipeline) but I think we should eventually decide on one package manager.

Copy link
Contributor Author

@enrico-kaack-comp enrico-kaack-comp Mar 18, 2025

Choose a reason for hiding this comment

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

good spot thank you, I changed it to npm ci. I will also follow up on a ticket with deciding for one package manager.

@enrico-kaack-comp enrico-kaack-comp merged commit 3cfa84d into main Mar 18, 2025
1 check passed
@enrico-kaack-comp enrico-kaack-comp deleted the chore--add-pipeline branch March 18, 2025 13:47
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