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

Publish to npm on PR tags #6

Merged
merged 18 commits into from
Apr 25, 2024
Merged

Publish to npm on PR tags #6

merged 18 commits into from
Apr 25, 2024

Conversation

shihanwan
Copy link
Contributor

No description provided.

- name: Setup
uses: ./tooling/github/setup

- name: Copy env
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@zlalvani do we even have a .env file for this repo?

Copy link
Collaborator

Choose a reason for hiding this comment

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

we don't

@shihanwan shihanwan force-pushed the publish-to-npm branch 2 times, most recently from 731a34d to 11808b0 Compare April 24, 2024 15:17
@shihanwan shihanwan requested review from noqcks and zlalvani and removed request for noqcks April 24, 2024 15:18
- name: Checkout
uses: actions/checkout@v4

- uses: pnpm/action-setup@v2
Copy link
Contributor

Choose a reason for hiding this comment

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

should it be this?

      - name: Setup
        uses: ./tooling/github/setup


- name: 🚀 Publish to npm
shell: bash
run: pnpm publish apps/cli
Copy link
Contributor

Choose a reason for hiding this comment

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

need to publish bumpgen-core as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Should we publish both separately then?

Copy link
Collaborator

Choose a reason for hiding this comment

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

yes, they should be separate

Copy link
Contributor Author

Choose a reason for hiding this comment

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

are they going to be published at the same time or should we have 2 publish workflows, one for cli one for core?

@shihanwan shihanwan merged commit bd15366 into main Apr 25, 2024
4 checks passed
@noqcks noqcks deleted the publish-to-npm branch April 29, 2024 15:35
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.

3 participants