* Revamp issue and pull request templates, other docs tweaks
`yarn test` now runs all of our tests.
* Remove generated files from the repository
* Update to new Signal support URL
* Prevent the 'Test failed 2 == 1' from test-release in CI
* Another attempt to fix grunt test-release on Appveyor
* grunt test-release: Fail build if test fails
* Lint fix, and move jshint earlier in CI process
I added the following sections based on the Android Repository:
- Contributing Bug reports
- Contributing Ideas
- Contributing Funds
The first two should be in the readme, so the issue tracker stays an issue tracker and does not mutate into a discussion forum.
The contributing funds additionally links to the BitHub blog post, so people can understand what it is and where their money goes.
// FREEBIE (although it looks like, BitHub isn't set up for this repo yet?)
Move the development setup instructions to CONTRIBUTING.md and add
some guidelines for pull requests and such.
README now contains crypto export notice, license, etc... Borrowed
heavily from the Signal-iOS readme.
Since I decided to preen mocha and chai, we can no longer generate the
concat file list from the preen config. We must instead explicitly list
the modules we want to concatenate. I placed this config in bower.json
so that most of the time, we won't need to change the Gruntfile.
Also added a concatenation task for test page dependencies.
To components. Because tab-completion works better when there aren't two
things starting with bower, and shorter names are nicer to deal with in
general.
Set up grunt with tasks for:
* preen - deletes unused files from bower_components, configured in
bower.json
* concat - concatenates preened bower components, configured
automagically from the preen config
It's worth noting that this setup assumes the order of files within a
package doesn't matter. This is usually true since we often include only
one file from the package.
