bors-ng
rust-cache
Our great sponsors
bors-ng | rust-cache | |
---|---|---|
14 | 6 | |
1,516 | 1,142 | |
- | - | |
7.2 | 7.3 | |
25 days ago | about 1 month ago | |
Elixir | TypeScript | |
Apache License 2.0 | GNU Lesser General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bors-ng
- Bors: Elixir GitHub bot that prevents merge skew / semantic merge conflicts
-
How do you WORK WITH testing teams?
You can further protect main branch by using a rollup approach (see Bors for an example) where the pre-merge tests are run against the combination of those PRs currently proposed for merging, which limits the possibility that two PRs look OK but together break something.
-
Bors-NG, declared to be feature frozen and deprecated
Completely independent implementations of the same underlying concept, one of which was written pretty much just for the rust project, and the other was written as a more general tool and service.
-
Merge Commit, Squash, or Rebase: how do you close Pull Requests on GitHub?
Merge commit (via bors) because I hate squash merges.
-
What’s a bors, and why (don’t) you want it?
Maybe the author does not know that there's https://bors.tech which is a publicly available Bors instance. There's absolutely no operational cost involved except for the initial setup.
-
Two Years and over 700 Websites Later
Or images. On pages like https://bors.tech and https://foodpartners.us the "bloat" is all images. The images are bigger than they were in the 1990's because they look better, even if you don't think they communicate more "information" people may still want them.
-
Ask HN: How are pull requests integrated in a repo with high commit frequency?
According to the README, it bisects. It doesn't matter much for me, though - the batches in our case were never big.
https://github.com/bors-ng/bors-ng/blob/master/README.md#how...
-
This is how auto-merge works at Bumble, how we optimised processes and removed restrictions on the number of tickets per day
Sounds like they settled on the bors model of a batching merge queue. Gitlab's merge trains instead speculatively run all of the merges at once which gives more precise data at a higher cost and longer time, if your number of parallel runners is limited.
- Launch HN: MergeQueue (YC S21) – Automate rebasing and merging for your codebase
rust-cache
-
cargo cache in docker rust:latest
In Github Actions we use swatinem/rust-cache. They have a pretty good explanation of what they are doing, and if that's not enough you can have a look at what the code is doing
-
cargo-semver-checks v0.18.0: rustdoc caching, new lints & more
Out of curiosity, does this play well with the Swatinem/rust-cache action? To improve CI cache performance, it's good practice to cache only dependencies' artifacts, and this action as such automatically cleans out the workspace local artifacts before populating the cache.
-
actions-rs Github Actions need more maintainers!!! OR to be replaced
I've migrated to https://github.com/dtolnay/rust-toolchain for managing rustup, and https://github.com/Swatinem/rust-cache for caching
-
GitHub Actions best practices for Rust projects
I'd also like to drop a recommendation to use https://github.com/Swatinem/rust-cache for caching cargo-related artifacts. I found it to be extremely pleasant to use and very easy to integrate into my CI pipelines.
-
How should I go about making Rust workflows go faster with CI's with GitHub Actions? Are there any cache actions for Rust or a place I could look for general optimizations?
There is an awesome github actions plugin that configures caching for `~/.cargo` and `target/`: https://github.com/Swatinem/rust-cache
-
Looking for guidance/review on my first library: stroke-rs
Really cool! A few ideas: - cargo publish it! It'd be good to set the license, description, repository, and readme fields in Cargo.toml. - Your lib.rs looks good - clean & simply exporting types. - You could consider exporting Point/PointN at your library root (e.g. pub use them in lib.rs). If you expect a type will pretty much always be used, it's nice to export it at the root. It also makes those types easier to find on docs.rs. - There is a nifty github actions plugin that caches the crates.io registry, and your dependencies: https://github.com/Swatinem/rust-cache.
What are some alternatives?
cargo-xtask
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
marge-bot - A merge-bot for GitLab
toolchain - 🛠️ GitHub Action for `rustup` commands
rust-toolchain - Concise GitHub Action for installing a Rust toolchain
htmlbutcher - HTMLButcher is an advanced HTML slicing tool
audit-check - 🛡️ GitHub Action for security audits
ZudVPN - A mobile application to deploy private VPN servers in the cloud with DNS ad-blocking and other features
cargo-deny-action - ❌ GitHub Action for cargo-deny 🦀
shipit-engine - Deployment coordination
github-script - Write workflows scripting the GitHub API in JavaScript