Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Activity for Iizukiā
Type | On... | Excerpt | Status | Date |
---|---|---|---|---|
Edit | Post #289927 |
Post edited: Added git references |
— | 7 months ago |
Edit | Post #289928 | Initial revision | — | 7 months ago |
Answer | — |
A: How to revert main branch to an earlier commit in git? With `git reset`, but first, you may want to save the current state in another branch: ```bash $ git switch main $ git branch backup-of-main ``` Now the (perhaps messed up) state is safely stored in branch `backup-of-main`, and you can always just switch back to it and have another swing. T... (more) |
— | 7 months ago |
Edit | Post #289927 | Initial revision | — | 7 months ago |
Question | — |
How to revert main branch to an earlier commit in git? How to move the `main` branch back to an earlier commit in git? (more) |
— | 7 months ago |
Edit | Post #289838 |
Post edited: |
— | 8 months ago |
Edit | Post #289839 |
Post edited: |
— | 8 months ago |
Edit | Post #289839 | Initial revision | — | 8 months ago |
Answer | — |
A: How to pass command line arguments when using cargo run? Specify your arguments after `--`: ```bash cargo run --offline -- --my-argument 42 ``` `--offline` is just an example of cargo's own argument. They are passed before `--`. `--my-argument` and `42` will be passed to your program. Source: The Cargo Book (more) |
— | 8 months ago |
Edit | Post #289838 | Initial revision | — | 8 months ago |
Question | — |
How to pass command line arguments when using cargo run? When developing a rust program you build and run using `cargo run`. However you cannot just append arguments to that as they will be caught (and likely rejected) by cargo itself. So how to pass arguments through cargo run to the actual program under development? (more) |
— | 8 months ago |
Edit | Post #289829 |
Post edited: |
— | 8 months ago |
Comment | Post #289829 |
Yes that's it. Probably one can delete any branch like this, but that's beyond this question. (more) |
— | 8 months ago |
Edit | Post #289829 |
Post edited: |
— | 8 months ago |
Edit | Post #289830 | Initial revision | — | 8 months ago |
Answer | — |
A: How to delete a local branch in git? The safe way: [[1]](https://git-scm.com/docs/git-branch#Documentation/git-branch.txt---delete) ```bash git branch --delete ``` It will fail if the branch isn't merged. If this is ok then you can delete it anyway like this: [[2]](https://git-scm.com/docs/git-branch#Documentation/git-branch.txt---... (more) |
— | 8 months ago |
Edit | Post #289829 | Initial revision | — | 8 months ago |
Question | — |
How to delete a local branch in git? How to delete a local git branch which hasn't been pushed to anywhere, and only exists locally? (more) |
— | 8 months ago |
Edit | Post #289571 |
Post edited: |
— | 9 months ago |
Edit | Post #289572 | Initial revision | — | 9 months ago |
Answer | — |
A: Tidy Ansible assert module loop output Use the `quiet` parameter: ```ansible - name: Assertions ansible.builtin.assert: that: - item quiet: true loop: "{{ loopitems }}" vars: loopitems: - true - true - false ``` This will produce the familiar one line outputs. (more) |
— | 9 months ago |
Edit | Post #289571 | Initial revision | — | 9 months ago |
Question | — |
Tidy Ansible assert module loop output Looping in Ansible usually produces a neat output of one line per iteration (per host): ```ansible ... ok: [Arch] => (item=something) ok: [Arch] => (item=somethingelse) ok: [Arch] => (item=yetanotherthing) ok: [Arch] => (item=thisbetterbethelastone) ok: [Arch] => (item=ohhnoitwasnt) ok: [Arch... (more) |
— | 9 months ago |
Comment | Post #289491 |
How does git actually handle incomplete (local) repositories? Given that commits are changesets, just cloning a few of the most recent changes wouldn't result in anything sensible.
So does it like create an archive of the history beyond the desired depth, and apply the most recent commits on that? (more) |
— | 9 months ago |
- ← Previous
- 1
- 2
- 3
- Next →