Comments (12)
FWIW, I'm currently using this for my CI pipelines to ensure the app is cached/avoid rebuilds on every run:
- name: Install cargo-machete
uses: baptiste0928/cargo-install@v2
with:
crate: cargo-machete
- name: Cargo machete
run: cargo machete
from cargo-machete.
I've also added support for cargo-machete to https://github.com/taiki-e/install-action.
- uses: taiki-e/install-action@v2
with:
tool: cargo-machete
- uses: actions-rs/cargo@v1
with:
command: machete
from cargo-machete.
I came across this a bit too late, this was something I did: https://github.com/vsuryamurthy/cargo-machete-action today. But agreed that it is simple enough that this is not really necessary.
from cargo-machete.
Thanks all, looks like it's simple enough to set up cargo-machete via CI actions now. There aren't many CLI options to pass, so unless somebody wanted to customize the action at a higher level, it seems fine to me to use those other actions. Closing.
from cargo-machete.
@vsuryamurthy That looks great! Would you like to upstream this action in this repository? I'd be happy to pick up the maintenance, and add options for the few CLI flags that we have.
Alternatively, we could also publicize your or the other sets of actions in this project's README.
from cargo-machete.
@vsuryamurthy That looks great! Would you like to upstream this action in this repository? I'd be happy to pick up the maintenance, and add options for the few CLI flags that we have.
Personally I find it hard when the actual package and its corresponding action are in different locations. So I would be happy to move the action here and help you maintain it as well.
How would you like to structure it though? As a separate directory called action?
from cargo-machete.
Sounds good, and I think that makes sense too: when updating the CLI options, it's simpler to update all things in one place.
How would you like to structure it though? As a separate directory called action?
If we can do that, and that doesn't make it harder to use, then it would be perfect indeed.
from cargo-machete.
Sounds good, and I think that makes sense too: when updating the CLI options, it's simpler to update all things in one place.
How would you like to structure it though? As a separate directory called action?
If we can do that, and that doesn't make it harder to use, then it would be perfect indeed.
I will test it locally with my repository and get back to you.
from cargo-machete.
@bnjbvr So it is possible to put it into a folder. The action if upstreamed would have a path like this
bnjbvr/cargo-machete/action@v1
from cargo-machete.
@vsuryamurthy Thanks for checking. What would it take to host it at the root? It would only add an extra actions.yml
file to the root folder, if I understand correctly? If so, then I think we can do that 👍
from cargo-machete.
@vsuryamurthy Thanks for checking. What would it take to host it at the root? It would only add an extra
actions.yml
file to the root folder, if I understand correctly? If so, then I think we can do that 👍
An actions.yml file and a readme update with explanation.
from cargo-machete.
That looks great, let's do that then!
from cargo-machete.
Related Issues (20)
- Feature Request: Optimize [build-dependencies] as well HOT 2
- [bug] missing field `version` - should not report HOT 6
- No logo / mascot HOT 1
- Investigate Nightly CI failure
- Is there a way to ignore a workspace member crate? HOT 2
- Github Action fails in CI on windows-latest HOT 2
- Falso positive when package name and lib name differ HOT 3
- [Rust 1.77.0] cargo machete --with-metadata panicking HOT 2
- Feature Idea: Centralized config file HOT 1
- --with-metadata false positive with build-dependencies HOT 2
- When no issues are found report message is incomplete.
- Add a benchmark
- `--with-metadata` does not correctly analyze build scripts HOT 1
- Related dependencies are signed as unused but they are not HOT 3
- Make github action take a `working_dir` argument HOT 1
- False positives for multi-dep single `use` statements HOT 1
- Create a docker image? HOT 4
- Support for skipping sub-directories HOT 1
- Respect the `members` field of a workspace Cargo.toml HOT 2
- actions-rs/cargo@v1 use Node12. Please update the following actions to use Node.js 16 HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cargo-machete.