this sets up a CI that always passes so we can use bors in this repository
It would be best if the CI ran a markdown checker. If someone is interested they
can send a follow-up PR
note that using bors will not be mandatory (it's not checking anything!) so
you can continue merging PRs manually
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/rust-embedded/awesome-embedded-rust/pull/154
**Author:** [@japaric](https://github.com/japaric)
**Created:** 3/6/2019
**Status:** ✅ Merged
**Merged:** 3/7/2019
**Merged by:** [@berkus](https://github.com/berkus)
**Base:** `master` ← **Head:** `ci`
---
### 📝 Commits (1)
- [`3303377`](https://github.com/rust-embedded/awesome-embedded-rust/commit/330337743e41447392fec9c06af9a5de35c525e0) set up CI
### 📊 Changes
**2 files changed** (+14 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `.github/bors.toml` (+0 -0)
➕ `.travis.yml` (+14 -0)
</details>
### 📄 Description
this sets up a CI that always passes so we can use bors in this repository
It would be best if the CI ran a markdown checker. If someone is interested they
can send a follow-up PR
note that using bors will *not* be mandatory (it's not checking anything!) so
you can continue merging PRs manually
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/rust-embedded/awesome-embedded-rust/pull/154
Author: @japaric
Created: 3/6/2019
Status: ✅ Merged
Merged: 3/7/2019
Merged by: @berkus
Base:
master← Head:ci📝 Commits (1)
3303377set up CI📊 Changes
2 files changed (+14 additions, -0 deletions)
View changed files
📝
.github/bors.toml(+0 -0)➕
.travis.yml(+14 -0)📄 Description
this sets up a CI that always passes so we can use bors in this repository
It would be best if the CI ran a markdown checker. If someone is interested they
can send a follow-up PR
note that using bors will not be mandatory (it's not checking anything!) so
you can continue merging PRs manually
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.