-
Notifications
You must be signed in to change notification settings - Fork 19
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
feat: build and publish test version on PRs #171
feat: build and publish test version on PRs #171
Conversation
It is done in the PR publish workflow
|
@@ -2,7 +2,7 @@ name: Build | |||
|
|||
on: | |||
pull_request: | |||
branches: [main, develop] | |||
branches: [main] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we have develop here? Since PRs are opened against develop.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new workflow does this as one of its steps, so I took it out of here since it would be doing the same thing twice.
test: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: actions/checkout@v3 | ||
- uses: actions/setup-node@v3 | ||
with: | ||
node-version: 16 | ||
cache: npm | ||
- run: npm ci | ||
# TODO: enable linting once ready | ||
# - run: npm run lint | ||
- run: npm test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yknl this is the bit that the other workflow is doing
…contract-call-fees Update dependencies and add Stacks api provider
This adds a publish step to PR builds (or if action is run manually on any branch) which publishes a test build to the package repository with a version
<current_package_version>-<commit_short_sha>
.