Merge #90

90: update repository details to new organisation r=killercup a=Dylan-DPC

<!--
Thank you for taking the time to contribute to this project!

To ease reviewing your changes and making sure we don't forget anything,  please
take a minute to check the following (remove lines that don't apply), and
replace this text with a description of what this PR does. Bonus points for
linking to issues! :)
-->

- [x] I have created tests for any new feature, or added regression tests for bugfixes.
- [x] `cargo test` succeeds
- [x] Clippy is happy: `cargo +nightly clippy` succeeds
- [x] Rustfmt is happy: `cargo +nightly fmt` succeeds
(all checks not needed)

Author: bors[bot]

CONTRIBUTING.md

@@ -28,5 +28,5 @@ When we're ready to release, a project owner should do the following
   - Identify what fixes, features, and breaking changes are in the release.
 - Run `cargo publish` (run `cargo login` first if needed)
 
-[Issues]: https://github.com/killercup/assert_cli/issues
-[TODO]: https://github.com/killercup/assert_cli/search?q=TODO
+[Issues]: https://github.com/assert-rs/assert_cli/issues
+[TODO]: https://github.com/assert-rs/assert_cli/search?q=TODO

Cargo.toml

@@ -4,8 +4,8 @@ version = "0.5.4"
 description = "Test CLI Applications."
 authors = ["Pascal Hertleif <killercup@gmail.com>", "Ed Page <eopage@byu.net>"]
 license = "MIT OR Apache-2.0"
-repository = "https://github.com/killercup/assert_cli.git"
-homepage = "https://github.com/killercup/assert_cli"
+repository = "https://github.com/assert-rs/assert_cli.git"
+homepage = "https://github.com/assert-rs/assert_cli"
 documentation = "http://docs.rs/assert_cli/"
 readme = "README.md"
 categories = ["development-tools::testing"]
@@ -29,4 +29,4 @@ skeptic = "0.13"
 skeptic = "0.13"
 
 [badges]
-travis-ci = { repository = "killercup/assert_cli" }
+travis-ci = { repository = "assert-rs/assert_cli" }

README.md

@@ -2,7 +2,7 @@
 
 > **Test CLI Applications** - This crate checks the output of a child process is as expected.
 
-[![Build Status](https://travis-ci.org/killercup/assert_cli.svg)][Travis]
+[![Build Status](https://travis-ci.org/assert-rs/assert_cli.svg)][Travis]
 [![Documentation](https://img.shields.io/badge/docs-master-blue.svg)][Documentation]
 ![License](https://img.shields.io/crates/l/assert_cli.svg)
 [![crates.io](https://img.shields.io/crates/v/assert_cli.svg)][Crates.io]
@@ -94,7 +94,7 @@ submitted for inclusion in the work by you, as defined in the Apache-2.0
 license, shall be dual licensed as above, without any additional terms or
 conditions.
 
-[Travis]: https://travis-ci.org/killercup/assert_cli
+[Travis]: https://travis-ci.org/assert-rs/assert_cli
 [Crates.io]: https://crates.io/crates/assert_cli
 [Documentation]: https://docs.rs/assert_cli
 [Environment]: https://github.com/Freyskeyd/environment

src/macros.rs

@@ -70,7 +70,7 @@ pub fn flatten_escaped_string(x: &str) -> Cow<str> {
 /// Inspect a single token and decide if it is safe to `stringify!`, without loosing
 /// information about whitespaces, to address [issue 22].
 ///
-/// [issue 22]: https://github.com/killercup/assert_cli/issues/22
+/// [issue 22]: https://github.com/assert-rs/assert_cli/issues/22
 ///
 /// Call like `__assert_single_token_expression!(@CHECK x)`, where `x` can be any token to check.
 ///