Skip to content

Conversation

@martingarn
Copy link

We wanted the ability to report on all of the unresolved refs. Added an options that would allow that and not exit on the first unresolved ref.

martingarn and others added 5 commits July 19, 2017 15:16
…d continue processing instead of throwing an error on first unresolved ref.
added NodeJS to technologies_used added Travis-ci.com to technologies_used
Copy link

@Piterden Piterden left a comment

Choose a reason for hiding this comment

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

Love YAML)) ❤️

*
* @type {boolean}
*/
onErrorThrow: true

Choose a reason for hiding this comment

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

Thanx for comments, friend))

@philsturgeon
Copy link
Member

To get a handle on this repo we're having to clear house a little. If you think this is still a useful and relevant change please can you rebase and update it? Might be a tricky job, might be easier to start over, it depends how much has changed.

Thank you for your time making this in the first place!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants