html-next / ember-cli-changelog Goto Github PK

When creating a new log, add the date to the title.

I'm not terribly familiar with what the exact format is for these messages....

It would be nice to be able to supply github oauth creds so that we can run this for private repos.

For some reason, the changes are not reported as me, rwwagner90, but as html-next instead. Need to investigate this and how we deal with people versus orgs.

My changelog.js looks just like the template but I'm running into:

You MUST include 'project' in the options passed to compareCommits.It should be the path to the project's git root.

There is no description of what the project config option is or what it should look like.

Any help would be appreciated. Along similar lines, where should I be going to documentation about how to use each hook / option?

Thanks.

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

I feel like there has to be some coordination between ember-cli-release and this changelog. It would be cool if ember-cli-release could actually create a github release. And then this could add the changelog to the release notes. Similar to how ember-cli does their releases.

Thoughts?

The problem is that ember-cli-release creates a release.js config file and then ember-cli-changelog tries to overwrite it. ember-cli-changelog should have correct release.js config file

Hi there!

For some reason, no changes are detected for my repo. Any ideas what this?

I attempted to create similar commit compare behavior to what the github API package provides for use locally so that any git installation could be supported from the initial release. Unfortunately, I've had to deactivate those code paths until nodegit provides stable binaries for more platforms. Currently, nodegit will error on any system not running a specific version of GCC, making it very difficult to simply drop into an existing project the way ember-cli-changelog should be capable of.

It is possible to modify a project's .travis.yml file to ensure that nodegit does not error when building for CI, but to do so requires having your CI solution build from scratch the proper versions of several major libaries as well as nodegit itself, a process which takes anywhere from 6-10min per test run. Given how unacceptable a time sink that is, I chose to deactivate all code using nodegit.

I'm open to suggestions for alternative node packages or approaches that aren't based on nodegit. It's likely that what should be done is what several other projects seem to have done: create a light git wrapper over CLI usage of git for node to use.

It would be nice to have a way to explicitly mark a PR or a commit as "meaningful for the log".

For jQuery / angular style, I think this would be the format:

(log) <type>(<scope>): <subject>

For Ember, I think it would be this:

[LOG <TYPE> <channel>]

For all commits, I think there should be an additional option via #:

Angular: <type>(<scope>): <subject containing #log>
Ember: [<TYPE> <channel>] <subject containging #log>

This is more an open question than an issue but it appears that, according to npm ignore rules, config/changelog.js file cannot be ignored.

This is not big deal but it means that all users of this addon will mandatorily package config/changelog.js, regardless of their own rules, which is, I guess, not expected.

Were you aware of that point? The only option is to rename this config file but I din't find a good name, yet 😕