Skip to content

Conversation

@jaebradley
Copy link
Contributor

@jaebradley jaebradley commented Nov 10, 2017

Implementation Details

Example Commit Process (npm run commit)

semantic-commit

@jaebradley jaebradley self-assigned this Nov 10, 2017
@coveralls
Copy link

Coverage Status

Coverage remained the same at 99.472% when pulling ace6beb on implement-semantic-release into 2461018 on master.

@jaebradley
Copy link
Contributor Author

jaebradley commented Nov 10, 2017

I implemented semantic-release on one of my node projects, requestbin-cli.

I was able to trigger a release
image

which had tags
image

from Travis-CI
image

...only thing is (of course there's at least one thing)

semantic-release requires node 8

image

@coveralls
Copy link

coveralls commented Nov 10, 2017

Coverage Status

Coverage remained the same at 99.472% when pulling fb09d48 on implement-semantic-release into 2461018 on master.

directories:
- ~/.npm

notifications:
Copy link
Contributor Author

Choose a reason for hiding this comment

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

There are also HipChat notifications that we should implement later (I just didn't have the HipChat authentication information)

@jaebradley
Copy link
Contributor Author

Pull Request Build Completed As Expected

image

@coveralls
Copy link

coveralls commented Nov 10, 2017

Coverage Status

Coverage remained the same at 99.472% when pulling 652066d on implement-semantic-release into 2461018 on master.

@jaebradley
Copy link
Contributor Author

FYI @michaelroytman let me know if you have any questions about how this works!

Copy link
Contributor

@arizzitano arizzitano left a comment

Choose a reason for hiding this comment

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

👍 Let's get this merged so we can start seeing it in action!

- arizzitano@edx.org
- jbradley@edx.org
on_success: always
on_failure: always
Copy link
Contributor

Choose a reason for hiding this comment

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

I figure we can adjust this once we get a feel for the notification emails and have ironed out any kinks.

Side question: do you know whether there's a way to send build failure emails to the person who merged the PR? Not a requirement for this PR (actually probably should go in a separate one) but a nice-to-have for the future.

"deploy-storybook": "storybook-to-ghpages",
"lint": "eslint --ext .js --ext .jsx .",
"precommit": "npm run lint",
"commit": "git-cz",
Copy link
Contributor

Choose a reason for hiding this comment

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

What's the expected behavior of this hook? I just did a test commit and it appeared to run but didn't seem to do anything. Do contributors need to install and run cz-cli locally?

Copy link
Contributor

Choose a reason for hiding this comment

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

Discussed in person; we will address this in a follow-on PR.

installed semantic-release package, added commit convential commit analyzer, updated travis yaml to
run semantic release after build success

fix(travis): add node 8 to travis configuration

fix(dependency): Missing @storybook/channels dependency that was causing build failures on Node 8
@jaebradley jaebradley force-pushed the implement-semantic-release branch from 652066d to 8de3944 Compare November 16, 2017 15:51
@coveralls
Copy link

coveralls commented Nov 16, 2017

Coverage Status

Coverage remained the same at 99.472% when pulling ace6beb on implement-semantic-release into 2461018 on master.

@jaebradley jaebradley merged commit 82a2129 into master Nov 16, 2017
@jaebradley jaebradley deleted the implement-semantic-release branch November 16, 2017 16:54
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.

4 participants