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

Fix prepare step causing false github warnings #87

Merged
merged 1 commit into from
Jun 7, 2020
Merged

Conversation

stephenh
Copy link
Owner

@stephenh stephenh commented Jun 7, 2020

No description provided.

@stephenh stephenh changed the title Send initial yarn install stderr to /dev/null to avoid false warnings. Fix prepare step causing false github warnings Jun 7, 2020
@@ -11,7 +11,7 @@ jobs:
- v1-dependencies-{{ checksum "package.json" }}
- v1-dependencies-

- run: yarn install || echo "ignore failure"
- run: yarn install
Copy link
Owner Author

Choose a reason for hiding this comment

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

@cliedeman fwiw this is where those false-positive failures were coming from; the github actions was picking up the stdout/stderr from this yarn install running prepare which was doing a yarn build "before we really wanted".

I was trying to use prepare as a "before publish" but not "after install", which looks like is not possible? So just taking out prepare for now and will use a more manual ./publish.sh.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ah super weird. Did not know it did that.

prepublishOnly might do what you want

Copy link
Owner Author

Choose a reason for hiding this comment

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

Ah I think so, thanks for pointing out prepublishOnly.

@stephenh stephenh merged commit 20436d6 into master Jun 7, 2020
@stephenh stephenh deleted the ignore-error branch June 7, 2020 20:47
zfy0701 added a commit to sentioxyz/ts-proto that referenced this pull request Jan 5, 2023
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